On 03/31/11 20:58, Barry Finkel wrote:
> On 03/31/11 13:17, bind-users-requ...@lists.isc.org wrote:
>> Hello,
>>
>> I get the following messages on the BIND server when I do a short name
>> nslookup from a client:
>>
>> Mar 31 14:08:04 jedi named[1299]: [ID 873579 daemon.info] network
>> unreachable resolving 'C.ROOT-SERVERS.NET/AAAA/IN':
>> 2001:500:1::803f:235#53
>> Mar 31 14:08:05 jedi named[1299]: [ID 873579 daemon.info] network
>> unreachable resolving 'I.ROOT-SERVERS.NET/AAAA/IN':
>> 2001:500:1::803f:235#53
>> Mar 31 14:08:07 jedi named[1299]: [ID 873579 daemon.info] network
>> unreachable resolving 'B.ROOT-SERVERS.NET/AAAA/IN': 2001:500:2f::f#53
>> Mar 31 14:08:07 jedi named[1299]: [ID 873579 daemon.info] network
>> unreachable resolving 'L.ROOT-SERVERS.NET/AAAA/IN': 2001:500:2f::f#53
>>
>> The config files are below, we are running BIND 9 on Solaris 10. We
>> currently have 2 domain names configured and on IP address on the BIND
>> server itself. Any ideas from the gurus??
>>
>> Thanks
>
> You do not have IPv6 connectivity from the DNS server to
> {C,I,B,L}.root-servers.net.
And is it possible to make BIND stop trying to use IPv6 at all? I'm in a
similar situation, I know I have connection issues and I simply want
bind to either not use IPv6 or at least prefer IPv4.
liste-on-v6 {none;} in named.conf does not help, and I'm not much
surprised, as it's about listening and not querying.
Torinthiel
signature.asc
Description: OpenPGP digital signature
_______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
