Bind9 Error Network Unreachable Resolving Ubuntu
Contents |
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 named error network unreachable resolving workings and policies of this site About Us Learn more about Stack Overflow error network unreachable resolving dnskey in the company Business Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users
Bind Network Unreachable Resolving
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:
Ubuntu Bind Disable Ipv6
Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Ubuntu DNS server working, but getting errors in syslog up vote 7 down vote favorite it's my first question to the forum here, so please go easy on me. I'm a Linux newbie and I experimented with setting up my own Ubuntu bind error (network unreachable) resolving server (server name : araliya, domain: autun.hom, IP: 192.168.1.99). I setup everything and installed bind9 to setup a DNS server using the tutorial posted here (How do I do a complete BIND9 DNS Server Configuration with a hostname?). Everything went actually very well, until the step at the very end, when I had to check whether the DNS server is working. When I gave the following command, I got a good output. > named-checkzone autun.hom /etc/bind/zones/db.autun.hom zone autun.hom /IN: loaded serial 2 Ok However, when I did the same thing for my reverse DNS lookup I got a slightly different answer. > named-checkzone autun.hom /etc/bind/zones/db.192 zone autun.hom /IN: loaded serial 1 Ok The tutorial said that the output of "named-checkzone" should be the same for forward and reverse lookup zones. But the "loaded serial" value I get is different between the two answers. When I followed all the other tests including, dig, hostname, nslookup, I get good output. In fact, my DNS server looks like it's working. When I checked the syslog, however, I get lots of errors: May 10 20:09:04 araliya
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the
Bind9 Disable Ipv6
workings and policies of this site About Us Learn more about Stack error (network unreachable) resolving debian Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags bind options="-4" Users Badges 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 http://askubuntu.com/questions/464163/ubuntu-dns-server-working-but-getting-errors-in-syslog 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 log file. They seem they can't resolve to certain addresses which I do not http://serverfault.com/questions/639061/network-unreachable-error-in-my-server-logs 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.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[15
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 http://www.centos.org/forums/viewtopic.php?t=8744 With Bind Quote Postby borish » 2013/07/28 15:03:45 Hi to you all,I have a problem with named.I install a new centos 6.3 server, installed bind on it, and at the begining 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 <<>> @192.168.1.190 network unreachable 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 {
listen-on port network unreachable resolving 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 {
type master;
file "haikin.local.rev";