why dig +trace does not working?
[r...@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 [r...@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 ;; QUESTION SECTION: ;35.com.IN A ;; ANSWER SECTION: 35.com. 100 IN A 210.75.241.83 ;; Query time: 2 msec ;; SERVER: 218.85.139.33#53(218.85.139.33) ;; WHEN: Sat Jun 12 11:34:14 2010 ;; MSG SIZE rcvd: 40 [r...@flyinweb ~]# dig @8.8.8.8 35.com +trace ; <<>> DiG 9.7.0-P2 <<>> @8.8.8.8 35.com +trace ; (1 server found) ;; global options: +cmd . 55672 IN NS m.root-servers.net. . 55672 IN NS k.root-servers.net. . 55672 IN NS g.root-servers.net. . 55672 IN NS c.root-servers.net. . 55672 IN NS d.root-servers.net. . 55672 IN NS a.root-servers.net. . 55672 IN NS i.root-servers.net. . 55672 IN NS h.root-servers.net. . 55672 IN NS j.root-servers.net. . 55672 IN NS l.root-servers.net. . 55672 IN NS b.root-servers.net. . 55672 IN NS e.root-servers.net. . 55672 IN NS f.root-servers.net. ;; Received 228 bytes from 8.8.8.8#53(8.8.8. in 97 ms com.172800 IN NS c.gtld-servers.net. com.172800 IN NS j.gtld-servers.net. com.172800 IN NS i.gtld-servers.net. com.172800 IN NS m.gtld-servers.net. com.172800 IN NS f.gtld-servers.net. com.172800 IN NS b.gtld-servers.net. com.172800 IN NS k.gtld-servers.net. com.172800 IN NS g.gtld-servers.net. com.172800 IN NS h.gtld-servers.net. com.172800 IN NS a.gtld-servers.net. com.172800 IN NS d.gtld-servers.net. com.172800 IN NS l.gtld-servers.net. com.172800 IN NS e.gtld-servers.net. ;; Received 512 bytes from 192.228.79.201#53(b.root-servers.net) in 194 ms 35.com. 172800 IN NS ns1.dns-diy.com. 35.com. 172800 IN NS ns2.dns-diy.com. ;; Received 164 bytes from 192.35.51.30#53(f.gtld-servers.net) in 196 ms 35.com. 100 IN A 210.75.241.83 ;; Received 40 bytes from 218.107.207.23#53(ns2.dns-diy.com) in 208 ms 2010-06-12 ShanyiWan ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: why dig +trace does not working?
So not awake, may be crazy... wkum...@xxx~$ dig @ns1.dns-diy.com 35.com ; <<>> DiG 9.4.2-P2.1 <<>> @ns1.dns-diy.com 35.com ; (1 server found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3253 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; WARNING: recursion requested but not available [SNIP] Se last line. W On Jun 11, 2010, at 11:41 PM, ShanyiWan wrote: [r...@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 [r...@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 ;; QUESTION SECTION: ;35.com.IN A ;; ANSWER SECTION: 35.com. 100 IN A 210.75.241.83 ;; Query time: 2 msec ;; SERVER: 218.85.139.33#53(218.85.139.33) ;; WHEN: Sat Jun 12 11:34:14 2010 ;; MSG SIZE rcvd: 40 [r...@flyinweb ~]# dig @8.8.8.8 35.com +trace ; <<>> DiG 9.7.0-P2 <<>> @8.8.8.8 35.com +trace ; (1 server found) ;; global options: +cmd . 55672 IN NS m.root-servers.net. . 55672 IN NS k.root-servers.net. . 55672 IN NS g.root-servers.net. . 55672 IN NS c.root-servers.net. . 55672 IN NS d.root-servers.net. . 55672 IN NS a.root-servers.net. . 55672 IN NS i.root-servers.net. . 55672 IN NS h.root-servers.net. . 55672 IN NS j.root-servers.net. . 55672 IN NS l.root-servers.net. . 55672 IN NS b.root-servers.net. . 55672 IN NS e.root-servers.net. . 55672 IN NS f.root-servers.net. ;; Received 228 bytes from 8.8.8.8#53(8.8.8. in 97 ms com.172800 IN NS c.gtld-servers.net. com.172800 IN NS j.gtld-servers.net. com.172800 IN NS i.gtld-servers.net. com.172800 IN NS m.gtld-servers.net. com.172800 IN NS f.gtld-servers.net. com.172800 IN NS b.gtld-servers.net. com.172800 IN NS k.gtld-servers.net. com.172800 IN NS g.gtld-servers.net. com.172800 IN NS h.gtld-servers.net. com.172800 IN NS a.gtld-servers.net. com.172800 IN NS d.gtld-servers.net. com.172800 IN NS l.gtld-servers.net. com.172800 IN NS e.gtld-servers.net. ;; Received 512 bytes from 192.228.79.201#53(b.root-servers.net) in 194 ms 35.com. 172800 IN NS ns1.dns-diy.com. 35.com. 172800 IN NS ns2.dns-diy.com. ;; Received 164 bytes from 192.35.51.30#53(f.gtld-servers.net) in 196 ms 35.com. 100 IN A 210.75.241.83 ;; Received 40 bytes from 218.107.207.23#53(ns2.dns-diy.com) in 208 ms 2010-06-12 ShanyiWan ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: why dig +trace does not working?
On 12/06/10 04:41, ShanyiWan wrote: [r...@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 [r...@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 ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: why dig +trace does not working?
On 12/06/10 10:48, Warren Kumari wrote: So not awake, may be crazy... wkum...@xxx~$ dig @ns1.dns-diy.com 35.com ; <<>> DiG 9.4.2-P2.1 <<>> @ns1.dns-diy.com 35.com ; (1 server found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3253 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; WARNING: recursion requested but not available [SNIP] Se last line. Ehm, no. With +trace, dig doesn't request recursion, but takes control of following the referral chain itself. Best regards Niall O'Reilly University College Dublin IT Services ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: why dig +trace does not working?
On Jun 14, 2010, at 4:39 AM, Niall O'Reilly wrote:
On 12/06/10 10:48, Warren Kumari wrote:
So not awake, may be crazy...
wkum...@xxx~$ dig @ns1.dns-diy.com 35.com
; <<>> DiG 9.4.2-P2.1 <<>> @ns1.dns-diy.com 35.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3253
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available
[SNIP]
Se last line.
Ehm, no.
With +trace, dig doesn't request recursion, but takes
control of following the referral chain itself.
Oh, hey yah, thats obvious... Well, I did mention that I was not
awake :-P
W
Best regards
Niall O'Reilly
University College Dublin IT Services
--
"Being the Fun-Police in the global Internet is a thankless - and
probably futile - task."
-- R. Whittle ("draft-whittle-sram-ip-forwarding-01.txt")
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
