Dns 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] Problem With Bind Quote Postby borish » 2013/07/28 15:03:45 Hi to you all,I named error network unreachable resolving have a problem with named.I install a new centos 6.3 server, installed bind on it, and bind error network unreachable resolving 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 error network unreachable resolving dnskey in 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//
// Provided by Red Hat bind lame servers error network unreachable resolving 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 "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
Named Network Unreachable Resolving Ipv6
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.Forwarders will do DNS resolution if your server cannot do that.-jorch Top borish Posts: 3 Joined: 2013/07/28 14:30:
network unreachable in /log/messages 6 posts / 0 new Log in or register to post comments Last post #1 Wed, 07/09/2014 - 07:46 drguild Bind 9, network unreachable in /log/messages Have a
Error (network Unreachable) Resolving Ubuntu
strange thing I run virtualmin on my system has bind etc setup error (network unreachable) resolving debian but I don't do any public DNS stuff its only for my local lan. I checked some logs out options="-4" of interest and noticed Bind9 is spewing network unreachable messages on load. The amount of messages is too long (a few hundred lines of it) so here is the start http://www.centos.org/forums/viewtopic.php?t=8744 of bind to a few of these messages. Everything is pretty much a default install my dms enteries are my ISP ones with my server (itself) 127.0.0.1 and 192.168.1.1 listed first. My search DNS server is set as itself was set to my isp for some reason I think postfix did that as I use my external hostname which is my-static-ip.ispdomain.com.au. Apart https://www.virtualmin.com/node/33657 fromt that I don't know how to fix this or turn whatever feature off if I don't need it. Any clues on this? Jul 7 20:51:42 server named[15364]: ----------------------------------------------------
Jul 7 20:51:42 server named[15364]: BIND 9 is maintained by Internet Systems Consortium,
Jul 7 20:51:42 server named[15364]: Inc. (ISC), a non-profit 501(c)(3) public-benefit
Jul 7 20:51:42 server named[15364]: corporation. Support and training for BIND 9 are
Jul 7 20:51:42 server named[15364]: available at https://www.isc.org/support
Jul 7 20:51:42 server named[15364]: ----------------------------------------------------
Jul 7 20:51:42 server named[15364]: adjusted limit on open files from 4096 to 1048576
Jul 7 20:51:42 server named[15364]: found 2 CPUs, using 2 worker threads
Jul 7 20:51:42 server named[15364]: using up to 4096 sockets
Jul 7 20:51:42 server named[15364]: loading configuration from '/etc/named.conf'
Jul 7 20:51:42 server named[15364]: reading built-in trusted keys from file '/etc/named.iscdlv.key'
Jul 7 20:51:42 server named[15364]: using default UDP/IPv4 port range: [1024, 65535]
Jul 7 20:51:42 server named[15364]: using default UDP/IPv6 port range: [1024, 65535]
Jul 7 20:51:42 server named[15364]: listening on IPv6 interfaces, port 53
Jul 7 20:51:42 server named[15364]: listening on IPv4
New Member Hi, I would like to get some ideas about troubleshooting this issue and resolve https://www.howtoforge.com/community/threads/solved-nameserver-not-working.70840/ it. I have a new install with Debian 8 which went OK. I am using NGINX, so I 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 network unreachable name servers by name, but cannot ping added websites or the main 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 network unreachable resolving 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 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:2