Dnsmasq+Unbound observations in 25.1.7

Started by OPNenthu, May 19, 2025, 07:13:28 PM

Previous topic - Next topic
I also saw the duplicate ipv6 dns server. For me it was fixed by just using a single ipv6 dns server option with interface set to any (not one per interface).
Hardware:
DEC740

May 25, 2025, 12:23:02 PM #76 Last Edit: May 27, 2025, 05:38:36 PM by meyergru
I would assume that to be a glitch in DNSmasq - it seems to do some (incorrect) automagic to cast the DHCP server option over to the RA, which really is a different thing that should be specified separately. In ISC DHCP and RADVD, the distinction is clear.

Maybe it is just that it appears both as RA and DHCPv6 option when specified per interface.
Intel N100, 4* I226-V, 2* 82559, 16 GByte, 500 GByte NVME, ZTE F6005

1100 down / 800 up, Bufferbloat A+

Quote from: Monviech (Cedrik) on May 23, 2025, 10:35:42 AMYou can additionally try out:

Code Select Expand
opnsense-patch https://github.com/opnsense/core/commit/3b8e4a6ab6f74c24eca3b34d8ae0370a4ce494b8
It should prevent SERVFAIL if an entry is known by dnsmasq because it will be authoritative for the local domain.

Just want to report that this patch fixed the (seemingly) strange DNS timeout issues I was having for local domains after switching to Unbound + Dnsmasq DHCP. Eventually traced it to Dnsmasq failing to resolve my local domains. The strange part is that it was intermittent. If I tried the request a few times it would eventually work. With the patch, everything seems to be working as expected.

Nice, thank you for testing this.
Hardware:
DEC740