pfsense 2.7.0-BETA

[johnpoz]

@stephenkwabena

Ok so unbound is running and your clients are pointing at it.. And it resolves its own name via ptr query.

Where are you unbound settings. At a loss to why you are showing ping from the diagnostics?

[stephenkwabena]

@johnpoz said in pfsense 2.7.0-BETA:

Where are you unbound settings

Please, can show me where to find the settings?

[johnpoz]

@stephenkwabena in the resolver

login-to-view

[stephenkwabena]

@johnpoz login-to-view login-to-view login-to-view

[stephenkwabena]

@johnpoz Another issue. I have upgraded to pfsense 2.7.0-BETA, when I added a new interface for Guest's or hotspot, there is no internet on that LAN.
Below are my configuration
login-to-view

My firewall rule for the guest or hotspot lan
login-to-view

My DHCP settings too
login-to-view

[A Former User]

@stephenkwabena

If not fixed and still relevant : have a look at the unbound service.

For a similar issue I had to enable "DNS Query Forwarding" where before the "DNS Query Forwarding" was not enable and never needed.

The pfsense box itself had a working DNS setup, but DHCP clients behind the pfsense box could not connect due to DNS not resolving addresses issues.

[stephenw10]

I see nothing here that indicates it's actually a DNS issue. It was just speculated that it might be a DNS problem.

How is it actually failing on clients behind pfSense?

[stephenkwabena]

@stephenw10 said in pfsense 2.7.0-BETA:

I see nothing here that indicates it's a DNS issue.

Yes, I can access pfsense GUI using the domain name I resolved (https://firewall.mydomain.com) same LAN.

[stephenw10]

OK so when you're testing from a client that cannot reach the internet how does it fail? What error do you see?

[stephenkwabena]

@stephenw10 said in pfsense 2.7.0-BETA:

What error do you see?

The only thing I get with a client connected via cable and wireless is "connected, no internet" but I can access the pfsense GUI

[stephenw10]

Ok, so if you try to ping google.com from that client how does it fail?

[stephenkwabena]

@stephenw10 said in pfsense 2.7.0-BETA:

Ok, so if you try to ping google.com from that client how does it fail?

login-to-view

[stephenw10]

OK that indicates a DNS failure.

So check pfSense can resolve locally. Make sure the client is actually using pfSense for DNS.

[stephenw10]

There are two threads for this with people contributing in each.

Lets's continue in the other thread: https://forum.netgate.com/topic/180907/pfsense-2-7-0-beta