Debian Named Error Network Unreachable Resolving
Contents |
Start here for a quick overview of the site Help Center Detailed answers to any named network unreachable resolving ipv6 questions you might have Meta Discuss the workings and policies of
Bind Error Network Unreachable Resolving
this site About Us Learn more about Stack Overflow the company Business Learn more about hiring error network unreachable resolving dnskey in developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system lame servers error network unreachable resolving and network administrators. 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 (network unreachable) error in my server logs up vote 3 down vote favorite 2 I'm getting lots of network
Named Disable Ipv6
unreachable lines in my Centos' messages 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) re
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 strange thing I run virtualmin on my ubuntu bind disable ipv6 system has bind etc setup but I don't do any public DNS stuff error (network unreachable) resolving ubuntu its only for my local lan. I checked some logs out of interest and noticed Bind9 is spewing network unreachable messages
Bind Options="-4"
on load. The amount of messages is too long (a few hundred lines of it) so here is the start of bind to a few of these messages. Everything is pretty much a http://serverfault.com/questions/639061/network-unreachable-error-in-my-server-logs 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 fromt that I don't know how to fix this or turn whatever feature off if I don't need it. https://www.virtualmin.com/node/33657 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 interface lo, 127.0.0.1#53
Jul 7 20:51:42 server named[15364]: listening on IPv4 interface eth0, 192.168.1.1#53
Jul 7 20:51:42 server named[15364]: generating session key for dynamic DNS
Jul 7 20:51:42 server named[15364]: sizing zone task pool based on 12 zones
New Member Hi, I would like to get some ideas about https://www.howtoforge.com/community/threads/solved-nameserver-not-working.70840/ troubleshooting this issue and resolve 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 network unreachable I can ping the servers IP and ping the 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 network unreachable resolving 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 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