dig +trace problem
Mark Andrews
Mark_Andrews at isc.org
Fri Apr 21 07:07:59 UTC 2006
> It worked for me. Are you doing this from somewhere internal to
> ymllabs.com? Perhaps you're not getting there the way you think.
>
> dig mail.ymllabs.com +trace +recurse
>
> ; <<>> DiG 9.2.1 <<>> mail.ymllabs.com +trace +recurse
> ;; global options: printcmd
> . 334665 IN NS G.ROOT-SERVERS.NET.
> . 334665 IN NS H.ROOT-SERVERS.NET.
> . 334665 IN NS I.ROOT-SERVERS.NET.
> . 334665 IN NS J.ROOT-SERVERS.NET.
> . 334665 IN NS K.ROOT-SERVERS.NET.
> . 334665 IN NS L.ROOT-SERVERS.NET.
> . 334665 IN NS M.ROOT-SERVERS.NET.
> . 334665 IN NS A.ROOT-SERVERS.NET.
> . 334665 IN NS B.ROOT-SERVERS.NET.
> . 334665 IN NS C.ROOT-SERVERS.NET.
> . 334665 IN NS D.ROOT-SERVERS.NET.
> . 334665 IN NS E.ROOT-SERVERS.NET.
> . 334665 IN NS F.ROOT-SERVERS.NET.
> ;; Received 260 bytes from 12.44.84.213#53(12.44.84.213) in 9 ms
>
> 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.
> 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.
> ;; Received 506 bytes from 192.112.36.4#53(G.ROOT-SERVERS.NET) in 60 ms
>
> ymllabs.com. 172800 IN NS ns.cyberwebglobal.info.
> ymllabs.com. 172800 IN NS ns2.cyberwebglobal.info.
> ;; Received 88 bytes from 192.5.6.30#53(A.GTLD-SERVERS.NET) in 30 ms
>
> mail.ymllabs.com. 300 IN A 210.212.104.19
> ymllabs.com. 300 IN NS ns.cyberwebglobal.info.
> ymllabs.com. 300 IN NS ns2.cyberwebglobal.info.
> ;; Received 104 bytes from 203.199.113.30#53(ns.cyberwebglobal.info) in
> 290 ms
Only GLUE A records exist for ns.cyberwebglobal.info and
ns2.cyberwebglobal.info. The A records which should also be
in the cyberwebglobal.info do not exist. If you have a IPv6
capable machine then named / dig will ask for the AAAA record
for these nameservers and get back a response which says that
the nameservers DO NOT EXIST.
If you are IPv4 only (or are lucky enough that the query pattern
gets the glue records) you will sometimes get a answer.
Mark
; <<>> DiG 9.3.2 <<>> ns.cyberwebglobal.info @203.199.113.30 +norec
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 12276
;; flags: qr aa; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;ns.cyberwebglobal.info. IN A
;; AUTHORITY SECTION:
cyberwebglobal.info. 300 IN SOA ns.cyberwebglobal.info. postmaster.cyberwebglobal.info. 2006041601 10800 3600 604800 300
;; Query time: 369 msec
;; SERVER: 203.199.113.30#53(203.199.113.30)
;; WHEN: Fri Apr 21 17:05:31 2006
;; MSG SIZE rcvd: 87
>
> -----Original Message-----
> From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On
> Behalf Of Carl Byington
> Sent: Thursday, April 20, 2006 11:44 AM
> To: comp-protocols-dns-bind at isc.org
> Subject: dig +trace problem
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On my system,
> "dig mail.ymllabs.com +trace +recurse"
> returns
> "couldn't get address for 'ns.cyberwebglobal.info': not found"
>
> Yet
> "host mail.ymllabs.com"
> after a bit of delay returns 210.212.104.19.
>
> I thought the above dig command should return that ip address. Am I
> misinterpreting the dig parameters, or is there something strange with
> that name?
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.6 (GNU/Linux)
>
> iD8DBQFER6wOL6j7milTFsERAko/AJ4hebCLKc7HmicvkRSh3FA++X6RWgCfbZ+v
> eOugQBCi6m86T7ul+S5b4aM=
> =RP9z
> -----END PGP SIGNATURE-----
>
>
>
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews at isc.org
More information about the bind-users
mailing list