Error Network Unreachable Resolving Bind9
Contents |
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings bind9 error network unreachable resolving ipv6 and policies of this site About Us Learn more about Stack Overflow
Named Error Network Unreachable Resolving
the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges error network unreachable resolving dnskey in Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works:
Lame Servers Error Network Unreachable Resolving
Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top (network unreachable) error in my server logs up vote 3 down vote favorite 2 I'm getting lots of network unreachable lines in my Centos' messages log file. They seem they can't resolve to certain addresses which I do not have any ideas bind network unreachable why my server has to resolve to them in the first place. Could anyone let me know the origin of such error? Am I under an attack? Oct 23 11:39:03 server named[1585]: error (network unreachable) resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53 Oct 23 11:39:03 server named[1585]: error (network unreachable) resolving './NS/IN': 2001:503:ba3e::2:30#53 Oct 23 11:39:03 server named[1585]: error (network unreachable) resolving 'dlv.isc.org/DNSKEY/IN': 2001:500:48::1#53 Oct 23 11:39:03 server named[1585]: error (network unreachable) resolving 'dlv.isc.org/DNSKEY/IN': 2001:4f8:0:2::19#53 Oct 23 11:39:03 server named[1585]: error (network unreachable) resolving 'ns.isc.afilias-nst.info/A/IN': 2001:500:2f::f#53 Oct 23 11:39:03 server named[1585]: error (network unreachable) resolving 'ns.isc.afilias-nst.info/AAAA/IN': 2001:500:2f::f#53 Oct 23 11:39:03 server named[1585]: error (network unreachable) resolving 'ns.isc.afilias-nst.info/A/IN': 2001:500:1::803f:235#53 Oct 23 11:39:03 server named[1585]: error (network unreachable) resolving 'ns.isc.afilias-nst.info/AAAA/IN': 2001:500:1::803f:235#53 Oct 23 11:39:03 server named[1585]: error (network unreachable) resolving 'ns.isc.afilias-nst.info/A/IN': 2001:503:c27::2:30#53 Oct 23 11:39:03 server named[1585]: error (network unreachable) resolving 'ns.isc.afilias-nst.info/AAAA/IN': 2001:503:c27::2:30#53 Oct 23 11:39:03 server named[1585]: error (network unreachable) resolving 'ns.isc.afilias-nst.info/A/IN': 2001:500:1a::1#53 Oct 23 11:39:03 server named[1585]: error (network unreachable) resolving 'dlv.isc.org/DNSKEY/IN': 2001:4f8:0:2::20#53 Oct 23 11:39:03 server named[1585]: error (network unreachable) resolving 'dlv.isc.org/DNSKEY/IN': 2001:500:60::29#53 Oct 23 11:39:03 server named[1585]: error (network unreachable) resolving 'ns1.isc.ultradns.net/A/IN': 2001:7fd::1#53 O
file (messages are slightly obfuscated to protect innocent :)): Jun 29 14:32:11 someserver named[1459]: error (network unreachable) resolving 'www.eolprocess.com/A/IN': 2001:503:a83e::2:30#53 Jun 29 14:32:11 someserver named[1459]: error (network unreachable) resolving 'www.eolprocess.com/A/IN': 2001:503:231d::2:30#53 What these messages say
Error (network Unreachable) Resolving Ubuntu
is that network that contains address 2001:503:231d::2:30 is unreachable. So, what's happening? The problem
Bind9 Disable Ipv6
is that all modern operating systems support IPv6 out of the box. The same is for growing number of software packages, ubuntu bind disable ipv6 among them is BIND too. So, operating system configures IPv6 address on interface and application thinks that IPv6 works and configures it. But, IPv6 doesn't work outside of the local network (there is no IPv6 capable http://serverfault.com/questions/639061/network-unreachable-error-in-my-server-logs router) so, IPv6 addresses, unless in local networks, are unreachable. So, you might ask now: but everything otherwise works, why is this case special! Well, the problem is that some DNS servers, anywhere in hierarchy, support IPv6, but not all. And when our resolver gets IPv6 address in response, it defaults to it and ignores IPv4. It obviously can not reach it so it logs a message and then tries IPv4. http://sgros.blogspot.com/2012/06/bind-and-network-unreachable-messages.html Once again, note that this IPv6 address can pop up anywhere in hierarchy, it isn't necessary to be on the last DNS server. In this concrete case name server for eolprocess.com doesn't support IPv6, but some name server for the top level com domain do support it! To prevent those messages from appearing add option -4 to bind during startup. On CentOS (Fedora/RHEL) add or modify the line OPTIONS in /etc/sysconfig/named so that it includes option -4, i.e. OPTIONS="-4" Posted by Stjepan Groš (sgros) at 14:49 Labels: bind, centos, dns, english, fedora, ipv4, ipv6, linux, named, netadm, network unreachable, problem, resolver, sysadm Location: Zagreb, Croatia 5 comments: joebuff said... /etc/sysconfing/named should be/etc/sysconfig/named January 8, 2014 at 2:15 PM Stjepan Groš (sgros) said... Fixed. Thanks. January 8, 2014 at 9:41 PM Richard Leji said... I really appreciate ur help! April 18, 2014 at 2:27 AM Илья Окатов said... where can disable this option in ubuntu? May 22, 2014 at 3:08 PM aber hallo said... /etc/default/bind9 :-) July 2, 2014 at 9:22 AM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) About Me Stjepan Groš (sgros) scientist, consultant, security specialist, networking guy, system administrator, philosopher ;) View my complete profile Blog Archive ► 2016 (10) ► September
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center http://askubuntu.com/questions/349757/error-network-unreachable-resolving-dnskey-in-20017fd153 Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is network unreachable a question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Error (network unreachable) resolving './DNSKEY/IN': 2001:7fd::1#53 up vote 1 error network unreachable down vote favorite I was trying to install dhcp3 server on Ubuntu 12.04 (Precise Pangolin) 32-bit server. Dhcp3 server is installed, but it can't find the dhcp3.conf file in folder /etc/dhcp3. I used the command tail -f /var/log/syslog which displays this message: Sep 25 08:23:05 ubuntu AptDaemon: INFO: Quitting was requested Sep 25 08:24:46 ubuntu named[1195]: error (network unreachable) resolving './DNSKEY/IN': 2001:7fd::1#53 Sep 25 08:24:46 ubuntu named[1195]: error (network unreachable) resolving './NS/IN': 2001:7fd::1#53 Sep 25 08:24:46 ubuntu named[1195]: error (network unreachable) resolving './DNSKEY/IN': 2001:500:2f::f#53 Sep 25 08:24:46 ubuntu named[1195]: error (network unreachable) resolving './NS/IN': 2001:500:2f::f#53 Sep 25 08:24:46 ubuntu named[1195]: error (network unreachable) resolving './DNSKEY/IN': 2001:500:3::42#53 Sep 25 08:32:51 ubuntu NetworkManager[1097]: