21.02(and p1) - Unbound DNS Lookup Fails for Host Overrides and DHCP Clients
-
I have several host overrides defined in Services / DNS Resolver / General Settings that worked fine in 2.4.5p1 but no longer resolve in 21.02 and 21.02p1. These are handy aliases for accessing various internal and external services. For example, the Comcast cable modem at 192.168.100.1 is configured internally as modem.local.lan. After upgrading pfSense, these hostnames no longer resolve to an IP using LAN DNS lookups or using Diagnostics / DNS Lookup in pfSense which now returns ‘Host "modem.local.lan" could not be resolved.’ I have made no changes to any of the DNS Resolver configs before, during, or after upgrading.
UPDATE: LAN DNS requests for both overridden hosts and DHCP alias hostnames are working after a forced config reload. But neither will resolve with the DNS Lookup tool but both will resolve with the Ping tool.
-
I edited just the Description field for each override entry, saved, reloaded, and they now work properly from the LAN. Not sure if something went askew or if problem will reappear on reboot.
Even though these DNS lookups work from the LAN they still won’t resolve from the pfSense Diagnostics / DNS Lookup tool. Oddly, the pfSense Diagnostics / Ping tool resolves them just fine. Looks like the DNS Lookup tool will only use the upstream specified DNS servers.
-
@plfinch Hi, look at world's most known file : /etc/hosts You'll find your overrides there. At the end.
Are you using the perfect Resolver settings ? ( hint : the default ones ).
Nothing changed neither added here : System > General Setup - the "DNS Server Settings" section ?
-
@gertjan DNS settings appear to be defaults and yes /etc/hosts has the override entries. I experienced 2 issues.
-
DNS overrides not resolving for hosts on LAN. This is working after I forced reload of override settings and has not recurred. But I need to check again after next reboot.
-
DNS overrides not resolving with pfSense Diagnostics / DNS Lookup tool. I cannot be sure if this worked prior to update but it doesn’t work now. Oddly, the pfSense Diagnostics / Ping tool resolves these hosts just fine. I would expect same behavior for both and consider this a bug. The pfSense DNS Lookup tool should resolve the same as pfSense gives LAN clients.
Additional info: The DHCP client alias names are also in /etc/hosts and are not resolved by the DNS Lookup tool but are resolved by the Ping tool. Looks like the DNS Lookup tool only uses the upstream DNS servers. Almost seems like the tool needs a switch to enable local DNS entries to mimic what LAN client requests would receive. More helpful would be to always show both the internal and upstream result.
-