Dns Bind Error Network Unreachable Resolving
Contents |
With Bind Issues related to configuring your network Post Reply Print view Search Advanced search 4 posts • Page 1 of 1 borish Posts: 3 Joined: 2013/07/28 14:30:03 [SOLVED] named error network unreachable resolving Problem With Bind Quote Postby borish » 2013/07/28 15:03:45 Hi to you all,I error network unreachable resolving dnskey in have a problem with named.I install a new centos 6.3 server, installed bind on it, and at the begining
Lame Servers Error Network Unreachable Resolving
every thing was OK.after that i installed some zone file, and the problem is that i can't resolve any out side address.when i make "dig @192.168.1.190 google.co.il" i get:; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.17.rc1.el6_4.4
Bind Options="-4"
<<>> @192.168.1.190 google.co.il; (1 server found);; global options: +cmd;; connection timed out; no servers could be reachedmy named.conf file:Code: Select all//
// Provided by Red Hat bind package to configure the ISC BIND named(8) DNS
// server as a caching only nameserver (as a localhost DNS resolver only).
//
// See /usr/share/doc/bind*/sample/ for example named configuration files.
//
options {
error (network unreachable) resolving ubuntu listen-on port 53 { 127.0.0.1;192.168.1.190; };
listen-on-v6 port 53 { none; };
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
memstatistics-file "/var/named/data/named_mem_stats.txt";
allow-query { localhost; any; };
recursion yes;
dnssec-enable yes;
dnssec-validation yes;
dnssec-lookaside auto;
/* Path to ISC DLV key */
bindkeys-file "/etc/named.iscdlv.key";
managed-keys-directory "/var/named/dynamic";
};
logging {
channel default_debug {
file "data/named.run";
severity dynamic;
};
};
zone "." IN {
type hint;
file "named.ca";
};
zone "haikin.local" IN {
type master;
file "haikin.local.fw";
allow-update { none;};
};
zone "1.168.192.in-addr.arpa" IN {
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]:
Ubuntu Bind Disable Ipv6
error (network unreachable) resolving 'www.eolprocess.com/A/IN': 2001:503:231d::2:30#53 What these messages say is that error (network unreachable) resolving debian network that contains address 2001:503:231d::2:30 is unreachable. So, what's happening? The problem is that all modern operating systems dnssec-enable support IPv6 out of the box. The same is for growing number of software packages, among them is BIND too. So, operating system configures IPv6 address on interface and application thinks http://www.centos.org/forums/viewtopic.php?t=8744 that IPv6 works and configures it. But, IPv6 doesn't work outside of the local network (there is no IPv6 capable 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 http://sgros.blogspot.com/2012/06/bind-and-network-unreachable-messages.html 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 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 t
New Member Hi, I would like to get some ideas about troubleshooting this issue and resolve it. I have a new install https://www.howtoforge.com/community/threads/solved-nameserver-not-working.70840/ with Debian 8 which went OK. I am using NGINX, so I http://askubuntu.com/questions/349757/error-network-unreachable-resolving-dnskey-in-20017fd153 had to improvise a little from the standard Server guide for Debian with Apache .... install. Glue settings are set up at the Domain manager and I can ping the servers IP and ping the name servers by name, but cannot ping added websites or the main network unreachable server address by name or of course browse the sites. Anything that is using DNS is broken. Logs show network unreachable and DNS client cache query failing with denied. ISPCONFIG DNS ZONE for server Code: A h1-server.com. 188.226.193.152 0 3600 A mail 188.226.193.152 0 3600 A www 188.226.193.152 0 3600 MX h1-server.com. mail.h1-server.com. 10 3600 NS h1-server.com. ns1.h1-server.com. 0 3600 error network unreachable NS h1-server.com. ns2.h1-server.com. 0 3600 ping from home desktop to server h1-server.com Code: ping: unknown host h1-server.com ping from home desktop to server ns2.h1-server.com Code: PING ns2.h1-server.com (188.226.193.152) 56(84) bytes of data. 64 bytes from 188.226.193.152: icmp_seq=1 ttl=48 time=164 ms 64 bytes from 188.226.193.152: icmp_seq=2 ttl=48 time=164 ms 64 bytes from 188.226.193.152: icmp_seq=3 ttl=48 time=164 ms Here are some logs I have. daemon.log Code: Aug 19 22:11:17 cirrus named[573]: error (network unreachable) resolving 'e.ntpns.org/A/IN': 2a01:608:ffff:a011::200#53 Aug 19 22:11:17 cirrus named[573]: error (network unreachable) resolving 'a.ntpns.org/A/IN': 2001:500:2e::1#53 Aug 19 22:11:17 cirrus named[573]: error (network unreachable) resolving 'i.ntpns.org/A/IN': 2a01:608:ffff:a011::200#53 Aug 19 22:11:17 cirrus named[573]: error (network unreachable) resolving 'i.ntpns.org/AAAA/IN': 2a01:608:ffff:a011::200#53 Aug 19 22:11:17 cirrus named[573]: error (network unreachable) resolving 'e.ntpns.org/AAAA/IN': 2a01:608:ffff:a011::200#53 Aug 19 22:11:17 cirrus named[573]: error (network unreachable) resolving 'e.ntpns.org/A/IN': 2001:500:2e::1#53 Aug 19 22:11:17 cirrus named[573]: error (network unreachable) resolving 'a.ntpns.org/AAAA/IN': 2001:500:2e::1#53 Aug 19 22:11:27 cirrus named[573]: error (network unreachable) resolving 'ntp.org/DS/IN': 2001:500:c::1#53 Aug 19 22:11:27 cirrus ntpd_intres[1258]: DNS 0.debian.pool.ntp.org -> 146.185.130.223 Aug 19 22:11:29 cirrus named[573]: client 67.215.86.19#54127 (ns1.h1-server.com): query (cache) 'ns1.h1-server.com/A/IN' denied Aug 19 22:11:29 cirrus named[
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 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 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 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]: