Confused A.server ?

lhcash at us.ibm.com lhcash at us.ibm.com
Thu Jul 13 19:04:37 UTC 2000




You spewed forth:

> When default server is auth01.dns.cube.com and root server A is asked for
> www00.com data it replies with:

> > root
> Default Server:  A.ROOT-SERVERS.NET
> Address:  198.41.0.4

> > www00.com
> Server:  A.ROOT-SERVERS.NET
> Address:  198.41.0.4
>
> CUBE.COM        nameserver = AUTH01.DNS.CUBE.COM
> CUBE.COM        nameserver = AUTH02.DNS.CUBE.COM
> AUTH01.DNS.CUBE.COM     internet address = 207.242.168.4
> AUTH02.DNS.CUBE.COM     internet address = 207.242.168.5
>
>
>
> But when default server is sirius.www00.com, The A server says :
> > root
> Default Server:  a.root-servers.net
> Address:  198.41.0.4
>
> > www00.com
> Server:  a.root-servers.net
> Address:  198.41.0.4
>
> Name:    www00.com.sirius.www00.com
> Served by:
> - AUTH02.DNS.CUBE.COM
>           207.242.168.5
>           WWW00.COM
> - SIRIUS.WWW00.COM
>           12.14.30.199
>           WWW00.COM
>
>
>
> Why do this two inquieryies does not match???
>
> alex

I'll take a crack at this...

1) use dig instead of nslookup.  When I do, here's what I get:

sandy at sedmz3:/home/sandy$ dig @a.root-servers.net www00.com ns in
+norecurse

; <<>> DiG 8.2 <<>> @a.root-servers.net www00.com ns in +norecurse
; (1 server found)
;; res options: init defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34796
;; flags: qr; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2
;; QUERY SECTION:
;;      www00.com, type = NS, class = IN

;; ANSWER SECTION:
www00.com.              2D IN NS        AUTH02.DNS.CUBE.COM.
www00.com.              2D IN NS        SIRIUS.www00.com.

;; ADDITIONAL SECTION:
AUTH02.DNS.CUBE.COM.    2D IN A         207.242.168.5
SIRIUS.www00.com.       2D IN A         12.14.30.199

;; Total query time: 361 msec
;; FROM: sedmz3 to SERVER: a.root-servers.net  198.41.0.4
;; WHEN: Thu Jul 13 18:56:53 2000
;; MSG SIZE  sent: 27  rcvd: 113

2) Include the text of your entire session - it looks like your two queries
 were done from separate systems, one with 'cube.com' first
in its domain search path...here's a dig for cube.com:

sandy at sedmz3:/home/sandy$ dig @a.root-servers.net cube.com ns in +norecurse


; <<>> DiG 8.2 <<>> @a.root-servers.net cube.com ns in +norecurse
; (1 server found)
;; res options: init defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53128
;; flags: qr; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2
;; QUERY SECTION:
;;      cube.com, type = NS, class = IN

;; ANSWER SECTION:
cube.com.               2D IN NS        AUTH01.DNS.cube.com.
cube.com.               2D IN NS        AUTH02.DNS.cube.com.

;; ADDITIONAL SECTION:
AUTH01.DNS.cube.com.    2D IN A         207.242.168.4
AUTH02.DNS.cube.com.    2D IN A         207.242.168.5

;; Total query time: 267 msec
;; FROM: sedmz3 to SERVER: a.root-servers.net  198.41.0.4
;; WHEN: Thu Jul 13 19:03:04 2000
;; MSG SIZE  sent: 26  rcvd: 104

If you look at your second query, notice that it's actually asking about
'www00.com.sirius.www00.com'.

Just guessing...

-Sandy

--
Sandy Cash
Systems Programmer/Systems Administrator/Unix Geek
Special Events Web Hosting Solutions Group
IBM (Research Triangle Park, NC)
lhcash at us.ibm.com
(919) 254-6482 t/l 444





More information about the bind-users mailing list