When you see messages like below in your bind named.d logs then you’ve a Jekyll and Hyde network config: part of it says it supports IPv6, but in reality doesn’t as “2001:500:127::30” is the IPv6 of the generic TLD servers.
In my case a brain-dead TP-Link switch.
04-Dec-2016 13:05:48.008 lame-servers: network unreachable resolving 'c.gtld-servers.net/AAAA/IN': 2001:500:127::30#53
04-Dec-2016 13:05:48.008 lame-servers: network unreachable resolving 'd.gtld-servers.net/AAAA/IN': 2001:500:127::30#53
04-Dec-2016 13:05:48.008 lame-servers: network unreachable resolving 'e.gtld-servers.net/AAAA/IN': 2001:500:127::30#53
04-Dec-2016 13:05:48.008 lame-servers: network unreachable resolving 'f.gtld-servers.net/AAAA/IN': 2001:500:127::30#53
04-Dec-2016 13:05:48.008 lame-servers: network unreachable resolving 'g.gtld-servers.net/AAAA/IN': 2001:500:127::30#53
04-Dec-2016 13:05:48.009 lame-servers: network unreachable resolving 'h.gtld-servers.net/AAAA/IN': 2001:500:127::30#53
04-Dec-2016 13:05:48.009 lame-servers: network unreachable resolving 'i.gtld-servers.net/AAAA/IN': 2001:500:127::30#53
04-Dec-2016 13:05:48.009 lame-servers: network unreachable resolving 'j.gtld-servers.net/AAAA/IN': 2001:500:127::30#53
04-Dec-2016 13:05:48.009 lame-servers: network unreachable resolving 'k.gtld-servers.net/AAAA/IN': 2001:500:127::30#53
04-Dec-2016 13:05:48.009 lame-servers: network unreachable resolving 'l.gtld-servers.net/AAAA/IN': 2001:500:127::30#53
04-Dec-2016 13:05:48.009 lame-servers: network unreachable resolving 'm.gtld-servers.net/AAAA/IN': 2001:500:127::30#53
...
04-Dec-2016 13:24:13.500 lame-servers: network unreachable resolving './NS/IN': 2001:500:2f::f#53
A temporary solution is to run bind named.d in -4
mode (see examples for RHEL, CENTOS and OpenSuSE in the links below), but the actual solution is to get IPv6 working properly.
–jeroen
Like this:
Like Loading...