Bug #6056
closed
DNS Resover after upgrade to RC
Added by Pol Bettinger over 9 years ago.
Updated over 9 years ago.
Description
after upgrade from 2.3.6 to RC, DNS resolving didn't work from my machines in the LAN anymore.
As i looked into it i saw that the there are now also local-link interfaces shown, but not selected.
Selcting the Local-Link interface and the machines were able to resolve DNS again.
Perhaps, it would be good that on the config upgrade the corresponding local-link interfaces would also be selected.
Files
upgrade from 2.2.6 of course not 2.3.6 :-(
Unbound never bound to link local IPs before. The fact they're there now and work is because of fixes in 2.3. I suspect the difference is what DNS server(s) your clients are pointing to. How is DNS being configured on your clients? DHCPv6 or from RAs or? If you're not sure, what type of IPv6 config is on your LAN, and how is the DHCPv6 Server and RAs configured for the LAN?
Never bound before? Strange.
My Samba 4 Server does DNS forwarding to the local-link IP of the pfsense interface. And that worked before, until I did the upgrade.
All the machines point to the Samba server for DNS resolving
Never bound to them specifically, that is. They were skipped in Unbound's config. #4021 has specifics on that.
If you had it bound to "all", it would work on the link local IPs. Did you have "all" chosen there?
No, hadn't chosen "all" I had selected the specific interfaces.
i added a part of the 2.2.6 config (Hoping it is the right one)
For me everything is indeed fine. I am happy with the 2.3 RC upgrade. The intention to open this bug was indeed that I thought that on 2.2.6 it also answered on the ipv6 (local-link) adress of an interface, if that specific interface was selected. and that now one has to select the local-link interface of that interface too, to get the same behavior as before.
- Assignee set to Chris Buechler
- Status changed from New to Closed
- Affected Version deleted (
2.3)
something else changed here outside the Unbound config and it's not clear what. That config doesn't bind to link local on 2.2.6, and the bindings on IPv4 and IPv6 are the same on 2.2.6 and after upgrade to 2.3 with that config.
Also available in: Atom
PDF
Updated by 
Updated by