Sysquery Errors

Mark.Andrews at nominum.com Mark.Andrews at nominum.com
Mon Nov 27 22:06:43 UTC 2000


	Below is the response to "dig ns . @a.root-servers.net".  You
	will note that the additional section contains the addresses
	of the root servers listed in the answer section.  To be able
	to do this the root servers all also server the root-servers.net
	zone which contains the addresses of the the root servers.  Note
	also the root servers have large TTL on both the NS and A records.

	Now your root servers also have to answer queries for your root
	NS's in a similar fashion.  i.e. both NS and A records with
	high TTLs.  Use "dig +norec ns . @<IP-ADDRESS-OF-ROOT-SERVER>"
	and look at the answer.  Does it meet the requirements?  Do
	all of your root servers return "good" answers.

	Mark

; <<>> DiG 8.3 <<>> ns . @a.root-servers.net 
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
;; flags: qr aa rd; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 13
;; QUERY SECTION:
;;	., type = NS, class = IN

;; ANSWER SECTION:
.			6D IN NS	A.ROOT-SERVERS.NET.
.			6D IN NS	H.ROOT-SERVERS.NET.
.			6D IN NS	C.ROOT-SERVERS.NET.
.			6D IN NS	G.ROOT-SERVERS.NET.
.			6D IN NS	F.ROOT-SERVERS.NET.
.			6D IN NS	B.ROOT-SERVERS.NET.
.			6D IN NS	J.ROOT-SERVERS.NET.
.			6D IN NS	K.ROOT-SERVERS.NET.
.			6D IN NS	L.ROOT-SERVERS.NET.
.			6D IN NS	M.ROOT-SERVERS.NET.
.			6D IN NS	I.ROOT-SERVERS.NET.
.			6D IN NS	E.ROOT-SERVERS.NET.
.			6D IN NS	D.ROOT-SERVERS.NET.

;; ADDITIONAL SECTION:
A.ROOT-SERVERS.NET.	5w6d16h IN A	198.41.0.4
H.ROOT-SERVERS.NET.	5w6d16h IN A	128.63.2.53
C.ROOT-SERVERS.NET.	5w6d16h IN A	192.33.4.12
G.ROOT-SERVERS.NET.	5w6d16h IN A	192.112.36.4
F.ROOT-SERVERS.NET.	5w6d16h IN A	192.5.5.241
B.ROOT-SERVERS.NET.	5w6d16h IN A	128.9.0.107
J.ROOT-SERVERS.NET.	5w6d16h IN A	198.41.0.10
K.ROOT-SERVERS.NET.	5w6d16h IN A	193.0.14.129
L.ROOT-SERVERS.NET.	5w6d16h IN A	198.32.64.12
M.ROOT-SERVERS.NET.	5w6d16h IN A	202.12.27.33
I.ROOT-SERVERS.NET.	5w6d16h IN A	192.36.148.17
E.ROOT-SERVERS.NET.	5w6d16h IN A	192.203.230.10
D.ROOT-SERVERS.NET.	5w6d16h IN A	128.8.10.90

;; Total query time: 496 msec
;; FROM: drugs.dv.isc.org to SERVER: a.root-servers.net  198.41.0.4
;; WHEN: Tue Nov 28 08:56:02 2000
;; MSG SIZE  sent: 17  rcvd: 436


> I have seen this error in the archives and the only response I have
> seen is that you must find out why the root server is not responding.
> The error looks like this:
> Nov 20 07:38:23 hqdns1 named[6418]: sysquery: no addrs found for root
> NS (svr006.tcs.treas.gov)
> Nov 20 07:38:23 hqdns1 named[6418]: sysquery: no addrs found for root
> NS (svr015.tcs.treas.gov)
> Nov 20 07:38:23 hqdns1 named[6418]: ns_req: no address for root server
> Nov 20 07:38:23 hqdns1 named[6418]: sysquery: no addrs found for root
> NS ()
> 
> So far in working with the engineers who run the root server have: I
> have run a sniffer when I am getting the error. Traffic appears normal.
> Queries and responses in both directions.
> I dumped the cache and database. The addresses were in the cache and
> the database files.
> I ran in debug (d2) and checked the output file. It is a big file. I
> found nothing abnormal.
> I am running BIND 8.2.2p5 on Solaris 2.7
> I am running on an intranet and my DNS is master to the domain. The
> root servers are for resolving inside of the intranet.
> Please help. Thank you.
> 
> 
> Sent via Deja.com http://www.deja.com/
> Before you buy.
> 
> 
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com



More information about the bind-users mailing list