New problem with "lame-server" after Dist-Upgrade

John Wobus jw354 at cornell.edu
Fri Jan 6 22:03:01 UTC 2012


On Dec 28, 2011, at 8:56 PM, Chris Buxton wrote:
> On Dec 24, 2011, at 4:50 PM, Michelle Konzack wrote:
>
>> Dec 25 01:39:02 storage000 named[29649]: lame-servers: info: error  
>> (network unreachable) resolving 'www4.l.google.com/AAAA/IN':  
>> 2001:503:231d::2:30#53
>> Dec 25 01:40:10 storage000 named[29649]: lame-servers: info: error  
>> (network unreachable) resolving 'ns2.roka.net/AAAA/IN':  
>> 2001:500:1::803f:235#53
>> Dec 25 01:40:10 storage000 named[29649]: lame-servers: info: error  
>> (network unreachable) resolving 'dns.roka.net/AAAA/IN':  
>> 2001:748:100:70::2#53
>> Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error  
>> (network unreachable) resolving 'www.kaleme.com/AAAA/IN':  
>> 2001:503:a83e::2:30#53
>> Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error  
>> (network unreachable) resolving 'pdns3.ultradns.org/A/IN':  
>> 2001:500:2f::f#53
>> Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error  
>> (network unreachable) resolving 'pdns4.ultradns.org/A/IN':  
>> 2001:500:2f::f#53
>> Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error  
>> (network unreachable) resolving 'pdns3.ultradns.org/AAAA/IN':  
>> 2001:503:c27::2:30#53
>> Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error  
>> (network unreachable) resolving 'pdns4.ultradns.org/AAAA/IN':  
>> 2001:503:ba3e::2:30#53
>> Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error  
>> (network unreachable) resolving 'pdns3.ultradns.org/A/IN':  
>> 2001:dc3::35#53
>> Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error  
>> (network unreachable) resolving 'pdns4.ultradns.org/A/IN':  
>> 2001:503:c27::2:30#53
>> Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error  
>> (network unreachable) resolving 'pdns4.ultradns.org/A/IN':  
>> 2001:503:ba3e::2:30#53
>> Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error  
>> (network unreachable) resolving 'pdns4.ultradns.org/A/IN':  
>> 2001:7fd::1#53
>> Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error  
>> (network unreachable) resolving 'pdns3.ultradns.org/AAAA/IN':  
>> 2001:7fd::1#53
>> Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error  
>> (network unreachable) resolving 'pdns5.ultradns.info/A/IN':  
>> 2001:500:19::1#53
>> Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error  
>> (network unreachable) resolving 'pdns5.ultradns.info/A/IN':  
>> 2001:500:1a::1#53
>> Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error  
>> (network unreachable) resolving 'pdns4.ultradns.org/AAAA/IN':  
>> 2001:500:40::1#53
>> Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error  
>> (network unreachable) resolving 'pdns4.ultradns.org/A/IN':  
>> 2001:502:4612::1#53
>
> That tells me your IPv6 connectivity is probably broken. Either fix  
> it or disable IPv6 in named by starting it with -4.
>


So Bind's 'lame' log line includes the concept of 'unreachable'?  I  
seem to recall
the definition 'delegation target that answers without aa'.

However, given the '(network unreachable)' comment, I agree with your  
diagnosis.

John Wobus
Cornell



More information about the bind-users mailing list