Over the weekend I did some 32-to-64 bit architecture upgrades on
NanoBSD systems with 64-bit hardware.
The migrations were seamless EXCEPT that in every case, the DNS
forwarder [sic] would fail to work unless selectively un-bound from IPv6
interfaces.
On all of the systems, there was at least one interface included by the
default "all" which is not dual-stack. I suspect this is why dnsmasq
was choking. HOWEVER, I bring it up here in the forum because the very
same configs would not cause DNS to choke if restored to 32-bit
architecture of the same version.
Strange.
In my case, I've switched those systems to use unbound/Resolver, and in
all cases, all systems with unbound don't need to be un-bound from IPv6
interfaces.
Most of these configs have been rolled forward since early 2.0, so I
suspect that there may be idiosyncrasies in the config (e.g. old
defaults) that might be responsible (e.g. settings that may not cause
this issue to express itself in a brand new install).
Any hypotheses of this weird observation?
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
