Bind9 Error Network Unreachable
Contents |
Start here for a quick overview of the site Help Center Detailed answers to any questions you bind network unreachable might have Meta Discuss the workings and policies of this site
Bind Network Unreachable Resolving
About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting
Bind Network Unreachable Ipv6
ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join
Error (network Unreachable) Resolving Ubuntu
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 (network unreachable) error in my server logs up vote 2 down vote favorite 2 I'm getting lots of network unreachable lines in my Centos' messages bind9 disable ipv6 log file. They seem they can't resolve to certain addresses which I do not have any ideas 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
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 is ubuntu bind disable ipv6 that network that contains address 2001:503:231d::2:30 is unreachable. So, what's happening? The problem is that bind options="-4" all modern operating systems support IPv6 out of the box. The same is for growing number of software packages, among them error (network unreachable) resolving debian 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 router) so, http://serverfault.com/questions/639061/network-unreachable-error-in-my-server-logs 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. Once again, note that http://sgros.blogspot.com/2012/06/bind-and-network-unreachable-messages.html 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 (1) ► July (1) ► June (1) ► M
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 https://ubuntuforums.org/showthread.php?t=1608673 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 a network unreachable 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 bind 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]:
Get Kubuntu Get Xubuntu Get Lubuntu Get UbuntuStudio Get Mythbuntu Get Edubuntu Get Ubuntu-GNOME Get UbuntuKylin Ubuntu Code of Conduct Ubuntu Wiki Community Wiki Other Support Launchpad Answers Ubuntu IRC Support AskUbuntu Official Documentation User Documentation Social Media Facebook Twitter Useful Links Distrowatch Bugs: Ubuntu PPAs: Ubuntu Web Upd8: Ubuntu OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search Forum The Ubuntu Forum Community Ubuntu Specialised Support Ubuntu Servers, Cloud and Juju Server Platforms [ubuntu] bind9 attempting ipv6 on ipv4 network Having an Issue With Posting ? Do you want to help us debug the posting issues ? < is the place to report it, thanks ! Results 1 to 4 of 4 Thread: bind9 attempting ipv6 on ipv4 network Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode October 29th, 2010 #1 DrJohn999 View Profile View Forum Posts Private Message Frothy Coffee! Join Date Oct 2007 Location Hyperspace Beans 185 DistroUbuntu 14.04 Trusty Tahr bind9 attempting ipv6 on ipv4 network After upgrading from 9.10 to 10.04, a hundred or so of (for example) Code: error (network unreachable) resolving '14.42.117.203.in-addr.arpa/PTR/IN': 2001:500:13::c7d4:35#53: 1 Time(s) messages appear in syslog each day. Each URL has from 2 - 6 attempts at various ipv6 addresses. My question is why is bind9 trying to resolve ipv6 addresses? I have done nothing to enable or disable ipv6 and thought that if not explicitly enabled I would not have to be concerned with it. It's only a small niggle, but I'm curious to know what's going on. Adv Reply October 29th, 2010 #2 r00tintheb0x View Profile View Forum Posts Private Message Just Give Me the Beans! Jo