Bug #14357
closed
Making Changes to DNS Resolution Behavior Causes DNS Servers to be Lost
0%
Description
If DNS servers are define by DHCP in pfSense Plus 23.05 and you change the DNS Resolution Behavior under System --> General Setup, the DNS servers will disappear until the WAN interface is down/upped or a DHCP release and renew is done.
Updated by Jim Pingle over 2 years ago
- Status changed from New to Feedback
I can't reproduce this here. Where exactly are they missing from?
If I change that mode from the default (use local, fall back to remote) to a different option like "use remote, ignore local", it all appears to be correct/working.
The DNS servers from DHCP/DCHP6 are still in /etc/resolv.conf, the /var/etc/*nameserver* files are still present, the DNS servers from DHCP still appear under Status > Interfaces.
Updated by Kris Phillips over 2 years ago
I'm no longer able to reproduce this. I was able to reliably get this to happen when flipping between between "Use Remote DNS Servers, Ignore Local DNS" and "Use local DNS, fall back to remote DNS" on the May 5th builds of the RC. The DNS servers would completely disappear from the dashboard when toggling and DNS resolution would fail for the firewall.
Testing on the May 13th build and I can no longer reproduce this, so not sure if something changed in the builds or unbound/something DNS-related got updated, but it appears to be good now.
Updated by Jordan G over 2 years ago
Not able to reproduce this either. Does the DNS server override pull different servers on your ATT interface?
Updated by Kris Phillips over 2 years ago
Jordan Greene wrote in #note-3:
Not able to reproduce this either. Does the DNS server override pull different servers on your ATT interface?
When I was testing before, it was on a 7100 that was behind a lab subnet, so no direct WAN connection was involved.
Updated by Jim Pingle over 2 years ago
- Status changed from Feedback to Closed
Closing this for now, if you can find a way to reproduce it, check the files in my comment above and see what the contents are at the time the problem occurs vs when operating normally.
You might have caught it at a weird time in the middle of a DHCP renewal or they could be a race condition around that.