Problems with BIND 9.2.2 on OS X

[David Botham]

bind-users-bounce at isc.org wrote on 10/29/2004 04:08:38 PM:
[clip para, see OP for details]
> 
> "
> 
> Here is a typical session showing two failures , followed by a success
> 
> 
> xserveg5:/Users/admin root# dig +trace www.thinksecret.com
> 
> ; <<>> DiG 9.2.2 <<>> +trace www.thinksecret.com
> ;; global options:  printcmd
> .                       514064  IN      NS      E.ROOT-SERVERS.NET.
> .                       514064  IN      NS      F.ROOT-SERVERS.NET.
> .                       514064  IN      NS      G.ROOT-SERVERS.NET.
> .                       514064  IN      NS      H.ROOT-SERVERS.NET.
> .                       514064  IN      NS      I.ROOT-SERVERS.NET.
> .                       514064  IN      NS      J.ROOT-SERVERS.NET.
> .                       514064  IN      NS      K.ROOT-SERVERS.NET.
> .                       514064  IN      NS      L.ROOT-SERVERS.NET.
> .                       514064  IN      NS      M.ROOT-SERVERS.NET.
> .                       514064  IN      NS      A.ROOT-SERVERS.NET.
> .                       514064  IN      NS      B.ROOT-SERVERS.NET.
> .                       514064  IN      NS      C.ROOT-SERVERS.NET.
> .                       514064  IN      NS      D.ROOT-SERVERS.NET.
> ;; Received 244 bytes from 192.168.0.2#53(192.168.0.2) in 1 ms

This answer came from (relied on the operation of) the name server running 
on 192.168.0.2#53

> 
> com.                    172800  IN      NS      G.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      H.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      I.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      J.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      K.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      L.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      M.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      A.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      B.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      C.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      D.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      E.GTLD-SERVERS.NET.
> com.                    172800  IN      NS      F.GTLD-SERVERS.NET.
> ;; Received 509 bytes from 192.203.230.10#53(E.ROOT-SERVERS.NET) in 188 
> ms
> 
> dig: Couldn't find server 'G.GTLD-SERVERS.NET': No address associated 
> with nodename

This failure is due to the fact that dig could not sucessfully perform an 
A RR query for the domain name 'G.GTLD-SERVERS.NET'.  You do not see that 
query in the output of a 'dig +trace...', but, if you use ethereal (or 
your fav sniffer) you will see the query to which I am referring.  You 
might be able to gather some insight as to what is happening that way...

I can send you an ethereal caputre file from my system off line if you 
like.  I captured the same query you made above and you can see the 
additional queries.

hth,

Dave...