why dig +trace does not working?

[Niall O'Reilly]

On 12/06/10 04:41, ShanyiWan wrote:
> [root at flyinweb ~]# dig @ns1.dns-diy.com 35.com +trace
>
> ;<<>>  DiG 9.7.0-P2<<>>  @ns1.dns-diy.com 35.com +trace
> ; (1 server found)
> ;; global options: +cmd
> ;; Received 17 bytes from 218.85.139.33#53(218.85.139.33) in 2 ms
>
> [root at flyinweb ~]# dig @ns1.dns-diy.com 35.com
>
> ;<<>>  DiG 9.7.0-P2<<>>  @ns1.dns-diy.com 35.com
> ; (1 server found)
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17492
> ;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

	It's working, exactly as you asked it to.

	By specifying '@ns1.dns-diy.com', you're telling dig where
	to start the trace.  Since this is one of the servers which
	is authoritative for the '35.com' zone, dig finds the result
	you asked for, and stops the trace right there.

	In your second example, you start the trace at 8.8.8.8, which
	isn't authoritative for the zone of interest, so dig follows
	the referral chain until it arrives at ns2.dns-diy.com, which
	is also authoritative, and so provides dig with the result
	you asked for.

	I hope this helps.


	Best regards
	Niall O'Reilly
	University College Dublin IT Services