sysquery: no addrs found for root NS (J.ROOT-SERVERS.NET) Please Help!
Dan Mahoney
google at gushi.org
Thu Mar 11 19:53:05 UTC 2004
I have a server that I run primary DNS servers from, and I also answer
public queries on these, so that people are able to temporarily point
at me when they register a domain, and work on their sites while the
DNS propagates.
The problem is, from reading this newsgroup, the forward-first option
is a little buggy.
Every once in a while (notably if the network has a moment of
downtime, or if there are latency issues), I'll get this in my logs:
messages.2:Mar 11 07:00:01 prime named[114]: sysquery: no addrs found
for root NS (I.ROOT-SERVERS.NET)
messages.2:Mar 11 07:00:01 prime named[114]: sysquery: no addrs found
for root NS (A.ROOT-SERVERS.NET)
messages.2:Mar 11 07:00:01 prime named[114]: sysquery: no addrs found
for root NS (H.ROOT-SERVERS.NET)
messages.2:Mar 11 07:00:01 prime named[114]: sysquery: no addrs found
for root NS (E.ROOT-SERVERS.NET)
messages.2:Mar 11 07:00:01 prime named[114]: sysquery: no addrs found
for root NS (C.ROOT-SERVERS.NET)
messages.2:Mar 11 07:00:01 prime named[114]: sysquery: no addrs found
for root NS (G.ROOT-SERVERS.NET)
messages.2:Mar 11 07:00:01 prime named[114]: sysquery: no addrs found
for root NS (F.ROOT-SERVERS.NET)
It's constant, over and over, and for EVERY root server, but it only
starts when network connectivity is lost for a minute or more (due to,
for example, a router reboot). It overwhelms syslogd, eats a ton of
CPU and increases the load so badly that sendmail shuts down and other
processes slow to a crawl. And if I kill and restart the process,
everything comes back fine. Note that a HUP doesn't fix it.
If it matters, my BIND's are statically linked. This happens once
every week to once every month, and it's not reproducible (sorry).
Would anyone be interested in a coredump or a debugging log?
NOTE: I have a total of THREE nameservers bound to different ips, with
similar config file, but usually, only one nameserver bombs (either of
the two.)
If I need to build one of these with debugging symbols, tell me and I
will. If I should just upgrade to bind 9, tell me and I'll look into
it (I couldn't easily find a guide to migrating).
This problem has plagued me across upgrades, and the answer can't be
"don't use forward-first", as that negates the whole use of the
feature.
My named.conf:
options {
directory "/etc/namedb";
forwarders {
65.125.224.20;
65.125.224.8;
};
notify yes;
allow-transfer {
208.23.118.172;
208.23.118.20;
208.23.118.8;
208.23.118.252;
65.125.224.8;
65.125.224.20;
198.63.17.18;
65.125.228.130;
65.125.228.131;
65.125.228.132;
127.0.0.1;
};
forward first;
statistics-file "/etc/namedb/s/stats.out";
listen-on {
65.125.228.132;
};
query-source address 65.125.228.132;
listen-on port 5353 {
127.0.0.1;
};
statistics-interval 0;
# recursion no;
};
zone "." {
type hint;
file "named.root";
};
zone "0.0.127.IN-ADDR.ARPA" {
type master;
file "localhost.rev";
};
zone "gushi.org" {
type slave;
file "/etc/namedb/s/gushi.org.hosts";
masters {
65.125.228.130;
};
};
zone "nightmask.net" {
type slave;
file "/etc/namedb/s/nightmask.net.hosts";
masters {
65.125.228.130;
};
};
*plus more similar zones*
My other named.conf:
options {
directory "/etc/namedb";
forwarders {
65.125.224.20;
65.125.224.8;
};
notify yes;
allow-transfer {
208.23.118.172;
63.163.4.222;
208.23.118.20;
208.23.118.8;
65.125.224.20;
65.125.224.8;
208.23.118.252;
65.125.228.130;
65.125.228.131;
65.125.228.132;
127.0.0.1;
};
forward first;
statistics-file "/etc/namedb/s/stats.out";
listen-on {
65.125.228.131;
};
};
zone "." {
type hint;
file "named.root";
};
zone "0.0.127.IN-ADDR.ARPA" {
type master;
file "localhost.rev";
};
zone "gushi.org" {
file "/etc/namedb/s/db.gushi.org";
type slave;
masters {
65.125.228.130;
};
};
zone "sleepycheetah.com" {
file "/etc/namedb/s/db.sleepycheetah.com";
type slave;
masters {
65.125.228.132;
};
};
My named.root:
; This file holds the information on root name servers needed to
; initialize cache of Internet domain name servers
; (e.g. reference this file in the "cache . <file>"
; configuration file of BIND domain name servers).
;
; This file is made available by InterNIC
; under anonymous FTP as
; file /domain/named.root
; on server FTP.INTERNIC.NET
;
; last update: Nov 5, 2002
; related version of root zone: 2002110501
;
;
; formerly NS.INTERNIC.NET
;
. 3600000 IN NS A.ROOT-SERVERS.NET.
A.ROOT-SERVERS.NET. 3600000 A 198.41.0.4
;
; formerly NS1.ISI.EDU
;
. 3600000 NS B.ROOT-SERVERS.NET.
B.ROOT-SERVERS.NET. 3600000 A 128.9.0.107
;
; formerly C.PSI.NET
;
. 3600000 NS C.ROOT-SERVERS.NET.
C.ROOT-SERVERS.NET. 3600000 A 192.33.4.12
;
; formerly TERP.UMD.EDU
;
. 3600000 NS D.ROOT-SERVERS.NET.
D.ROOT-SERVERS.NET. 3600000 A 128.8.10.90
;
; formerly NS.NASA.GOV
;
. 3600000 NS E.ROOT-SERVERS.NET.
E.ROOT-SERVERS.NET. 3600000 A 192.203.230.10
;
; formerly NS.ISC.ORG
;
. 3600000 NS F.ROOT-SERVERS.NET.
F.ROOT-SERVERS.NET. 3600000 A 192.5.5.241
;
; formerly NS.NIC.DDN.MIL
;
. 3600000 NS G.ROOT-SERVERS.NET.
G.ROOT-SERVERS.NET. 3600000 A 192.112.36.4
;
; formerly AOS.ARL.ARMY.MIL
;
. 3600000 NS H.ROOT-SERVERS.NET.
H.ROOT-SERVERS.NET. 3600000 A 128.63.2.53
;
; formerly NIC.NORDU.NET
;
. 3600000 NS I.ROOT-SERVERS.NET.
I.ROOT-SERVERS.NET. 3600000 A 192.36.148.17
;
; operated by VeriSign, Inc.
;
. 3600000 NS J.ROOT-SERVERS.NET.
J.ROOT-SERVERS.NET. 3600000 A 192.58.128.30
;
; housed in LINX, operated by RIPE NCC
;
. 3600000 NS K.ROOT-SERVERS.NET.
K.ROOT-SERVERS.NET. 3600000 A 193.0.14.129
;
; operated by IANA
;
. 3600000 NS L.ROOT-SERVERS.NET.
L.ROOT-SERVERS.NET. 3600000 A 198.32.64.12
;
; housed in Japan, operated by WIDE
;
. 3600000 NS M.ROOT-SERVERS.NET.
M.ROOT-SERVERS.NET. 3600000 A 202.12.27.33
; End of File
More information about the bind-users
mailing list