Error Network Unreachable Resolving Bind
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] Problem With Bind Quote Postby borish » 2013/07/28 15:03:45 Hi to error network unreachable resolving dnskey in you all,I have a problem with named.I install a new centos 6.3 server, installed
Lame Servers Error Network Unreachable Resolving
bind on it, and at the begining every thing was OK.after that i installed some zone file, and the problem is that i
Named Network Unreachable Resolving Ipv6
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 <<>> @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//
Error (network Unreachable) Resolving Ubuntu
/>// 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 {
listen-on port 53 { 127.0.0.1;192.168.1.190; };
listen-on-v6 port 53 { none; };
directory "/var/named";
dump-file bind9 disable ipv6 "/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 {
type master;
file "haikin.local.rev";
allow-update { none; };
};
include "/etc/named.rfc1912.zones";
include "/etc/named.root.key";
Can you please HELP me !!Thank you. Top jorch Posts: 5 Joined: 2013/07/23 11:55:54 [SOLVED] Problem With Bind Quote Postby jorch » 2013/07/30 07:35:04 Hi,If you do not plan to run root name server then add forwarders { YOUR-ISP-DNS-1; YOUR-ISP-DNS-2;};forward first;to your options block and restart named.Forw
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 ubuntu bind disable ipv6 unreachable) resolving 'www.eolprocess.com/A/IN': 2001:503:231d::2:30#53 What these messages say is that network that contains bind options="-4" address 2001:503:231d::2:30 is unreachable. So, what's happening? The problem is that all modern operating systems support IPv6 out of error (network unreachable) resolving debian 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 that IPv6 works and http://www.centos.org/forums/viewtopic.php?t=8744 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 when our resolver gets IPv6 address http://sgros.blogspot.com/2012/06/bind-and-network-unreachable-messages.html 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 this option in ubuntu? May 22, 2014 at 3:08 PM aber hallo said... /etc
resolving 'www.SOME-DOMAIN.com/A/IN': :::#53 Edit /etc/default/bind9 and network unreachable add "-4" to the options so BIND9 does not resolve IPV6 (unless network unreachable resolving you have IPV6 connectivity, but in that case you shouldn't see this message aniway). Your OPTIONS line should look like this: OPTIONS="-u bind -4" . Prev Up NextChapter 8. Errors Home 8.3. managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found