what does dig +trace do?
TomSchmitt at gmx.de
Wed Aug 31 15:36:46 UTC 2011
> >> What strikes me as odd is that the first query does return 4 (internal)
> >> root servers, but no glue records ?
> >I have no idea why this is this way.
> Because +trace only displays the answer section of the responses by
> Try "dig +trace +additional".
you are right, thank you. With this I see the glue records:
; <<>> DiG 9.8.0-P4 <<>> +trace example.com
;; global options: +cmd
. 10800 IN NS root1.
. 10800 IN NS root2.
. 10800 IN NS root3.
. 10800 IN NS root4.
root1. 10800 IN A 10.111.111.111
root2. 10800 IN A 10.111.112.112
root3. 10800 IN A 10.111.113.113
root4. 10800 IN A 10.111.114.114
;; Received 159 bytes from 127.0.0.1#53(127.0.0.1) in 1 ms
;; connection timed out; no servers could be reached
The main problem is still the same though. The trace option fails with a timeout. Even thought I'm operating on the shell of one of the root-servers itself (so there is not much network in between to cause trouble).
NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie!
Jetzt informieren: http://www.gmx.net/de/go/freephone
More information about the bind-users