Why "dig foo" fails but "dig +trace foo" succeeds?
Norman Joseph
joseph at ctc.com
Tue Nov 16 17:12:36 UTC 2004
Is there anyone who can explain this behavior to me?
# dig www.powweb.com
<...waits patiently...>
; <<>> DiG 9.2.4rc6 <<>> www.powweb.com
;; global options: printcmd
;; connection timed out; no servers could be reached
#
# dig +trace www.powweb.com
; <<>> DiG 9.2.4rc6 <<>> +trace www.powweb.com
;; global options: printcmd
. 502538 IN NS K.ROOT-SERVERS.NET.
. 502538 IN NS L.ROOT-SERVERS.NET.
. 502538 IN NS M.ROOT-SERVERS.NET.
. 502538 IN NS A.ROOT-SERVERS.NET.
. 502538 IN NS B.ROOT-SERVERS.NET.
. 502538 IN NS C.ROOT-SERVERS.NET.
. 502538 IN NS D.ROOT-SERVERS.NET.
. 502538 IN NS E.ROOT-SERVERS.NET.
. 502538 IN NS F.ROOT-SERVERS.NET.
. 502538 IN NS G.ROOT-SERVERS.NET.
. 502538 IN NS H.ROOT-SERVERS.NET.
. 502538 IN NS I.ROOT-SERVERS.NET.
. 502538 IN NS J.ROOT-SERVERS.NET.
;; Received 372 bytes from 147.160.1.6#53(147.160.1.6) in 1 ms
com. 172800 IN NS a.gtld-servers.net.
com. 172800 IN NS g.gtld-servers.net.
com. 172800 IN NS h.gtld-servers.net.
com. 172800 IN NS c.gtld-servers.net.
com. 172800 IN NS i.gtld-servers.net.
com. 172800 IN NS b.gtld-servers.net.
com. 172800 IN NS d.gtld-servers.net.
com. 172800 IN NS l.gtld-servers.net.
com. 172800 IN NS f.gtld-servers.net.
com. 172800 IN NS j.gtld-servers.net.
com. 172800 IN NS k.gtld-servers.net.
com. 172800 IN NS e.gtld-servers.net.
com. 172800 IN NS m.gtld-servers.net.
;; Received 504 bytes from 193.0.14.129#53(K.ROOT-SERVERS.NET) in 87 ms
powweb.com. 172800 IN NS ns2.powweb.com.
powweb.com. 172800 IN NS ns3.powweb.com.
;; Received 100 bytes from 192.5.6.30#53(a.gtld-servers.net) in 22 ms
www.powweb.com. 3600 IN A 66.152.97.130
powweb.com. 3600 IN NS ns3.powweb.com.
powweb.com. 3600 IN NS ns2.powweb.com.
;; Received 116 bytes from 66.152.97.4#53(ns2.powweb.com) in 81 ms
If it matters, this is on RHEL 3.0.
More information about the bind-users
mailing list