dns errors related to ipv6

D

ditto

Verified User
Joined
Apr 27, 2009
Messages
1,980
Ever since I upgraded from CentOS 6.2 to CentOS 6.3 in july 2012, I have been getting these errors regarding named in logwatch report every day:

Code: 
error (network unreachable) resolving 'dlv.isc.org/DNSKEY/IN': 2001:4f8:0:2::19#53: 5 Time(s)
error (network unreachable) resolving 'dlv.isc.org/DNSKEY/IN': 2001:4f8:0:2::20#53: 7 Time(s)
error (network unreachable) resolving 'dlv.isc.org/DNSKEY/IN': 2001:500:2c::254#53: 4 Time(s)
error (network unreachable) resolving 'dlv.isc.org/DNSKEY/IN': 2001:500:60::29#53: 6 Time(s)
error (network unreachable) resolving 'dlv.isc.org/DNSKEY/IN': 2001:500:60::30#53: 5 Time(s)
error (network unreachable) resolving 'dlv.isc.org/DNSKEY/IN': 2001:500:71::29#53: 6 Time(s)
error (network unreachable) resolving 'dlv.isc.org/DNSKEY/IN': 2001:500:71::30#53: 5 Time(s)
error (network unreachable) resolving 'dlv.isc.org/DNSKEY/IN': 2001:500:c::1#53: 1 Time(s)
error (network unreachable) resolving 'ns.isc.afilias-nst.info/A/IN': 2a01:8840:9::1#53: 1 Time(s)
error (network unreachable) resolving 'ns.isc.afilias-nst.info/AAAA/IN': 2a01:8840:9::1#53: 1 Time(s)
error (network unreachable) resolving 'ns1.isc.ultradns.net/A/IN': 2001:502:f3ff::1#53: 5 Time(s)
error (network unreachable) resolving 'ns1.isc.ultradns.net/A/IN': 2610:a1:1014::1#53: 2 Time(s)
error (network unreachable) resolving 'ns1.isc.ultradns.net/A/IN': 2610:a1:1015::1#53: 1 Time(s)
error (network unreachable) resolving 'ns1.isc.ultradns.net/A/IN': 2610:a1:1016::1#53: 2 Time(s)
error (network unreachable) resolving 'ns1.isc.ultradns.net/AAAA/IN': 2001:502:f3ff::1#53: 4 Time(s)
error (network unreachable) resolving 'ns1.isc.ultradns.net/AAAA/IN': 2610:a1:1014::1#53: 1 Time(s)
error (network unreachable) resolving 'ns1.isc.ultradns.net/AAAA/IN': 2610:a1:1015::1#53: 1 Time(s)
error (network unreachable) resolving 'ns1.isc.ultradns.net/AAAA/IN': 2610:a1:1016::1#53: 2 Time(s)
error (network unreachable) resolving 'ns2.isc.ultradns.net/A/IN': 2001:502:f3ff::1#53: 5 Time(s)
error (network unreachable) resolving 'ns2.isc.ultradns.net/A/IN': 2610:a1:1014::1#53: 2 Time(s)
error (network unreachable) resolving 'ns2.isc.ultradns.net/A/IN': 2610:a1:1015::1#53: 1 Time(s)
error (network unreachable) resolving 'ns2.isc.ultradns.net/A/IN': 2610:a1:1016::1#53: 2 Time(s)
error (network unreachable) resolving 'ns2.isc.ultradns.net/AAAA/IN': 2001:502:f3ff::1#53: 5 Time(s)
error (network unreachable) resolving 'ns2.isc.ultradns.net/AAAA/IN': 2610:a1:1014::1#53: 2 Time(s)
error (network unreachable) resolving 'ns2.isc.ultradns.net/AAAA/IN': 2610:a1:1015::1#53: 1 Time(s)
error (network unreachable) resolving 'ns2.isc.ultradns.net/AAAA/IN': 2610:a1:1016::1#53: 2 Time(s)
error (network unreachable) resolving 'pdns3.ultradns.org/AAAA/IN': 2610:a1:1015::1#53: 1 Time(s)

I posted about it here http://forum.directadmin.com/showthread.php?t=44072&p=224926#post224926

However I still have not fixed this. Everything is working without problems. I have three servers, one of them wich is IPV6 ready do not get these errors, but the two other servers wich is not IPV6 ready, get those errors in logwatch report every morning.

When I search for answers, I have found in other forums that they recommend to add OPTIONS="-4" to /etc/sysconfig/named, is that a good idea? Does anybody else get these errors, and how do you solve it? Here is a quote (I don't want to link to it, because it is to a forum for a competitor to DirectAdmin):

To fix this you have to start the bind damon with "-4" (IPv4 only). You can add the line "OPTIONS="-4"" to /etc/sysconfig/named to do so.
Click to expand...
 
Thank you for the confirmation. I have now added OPTIONS="-4" to named, and restarted named. It seems to work fine without problems.

Edit: Also this seems to have made the DirectAdmin control planel faster loading! I am running DirectAdmin on https. Strange, but I really notice a difference, it loads the pages in DirectAdmin control panel faster then ever after this change! :)
 
Last edited:
Maybe your server has an ipv6 address assigned and is trying to contact these dns servers over ipv6.
Maybe thats why it was slow.

Try to remove the faulty ipv6 configuration.
 
It was not slow before. I do not have any ipv6 address assigned the two servers this was about. If I did have, then there would be no problems. I have another server wich is ipv6 ready, wich did not get these errors. Anyway. The problem is solved the way described above. When I add ipv6 addresses to the server in the future, I will of course need to remove OPTIONS="-4" from named.
 
You must log in or register to reply here.
Back
Top