I've just upgraded the first of my redundant slave DNS servers from Debian 10.11 (bind 9.11) to Debian 11.2 (bind 9.16). Upgrade seemed to go smoothly but I'm now seeing the below in the bind logs
22-Feb-2022 14:54:59.745 lame-servers: info: timed out resolving 'ns4.he.net/AAAA/IN': 1.1.1.1#53 22-Feb-2022 14:54:59.745 lame-servers: info: network unreachable resolving 'ns4.he.net/AAAA/IN': 2001:500:200::b#53 22-Feb-2022 14:54:59.745 lame-servers: info: network unreachable resolving 'ns4.he.net/AAAA/IN': 2001:500:9f::42#53 22-Feb-2022 14:54:59.745 lame-servers: info: network unreachable resolving 'ns4.he.net/AAAA/IN': 2001:500:2d::d#53 22-Feb-2022 14:55:07.155 dnssec: warning: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out If I run a nslookup against any of the time out's in the logs, it works and delivers both the ipv4 and ipv6 address I've done some reading on the issue and so far, found that I can add a couple of lines to /etc/sysctl.conf and named.conf to disable ipv6 but I'd much rather get the system to handle ipv6 properly and am looking for your advice on this. Thanks in advance Andy Baker
-- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
