Bind 9.3.2 - how do i know dns is using which root server
Alex Tang
alextang at cms.hkcable.com
Thu Mar 9 10:53:58 UTC 2006
Dear Sir
I start the bind with a debug level 11 but cannot find out which root server replied the ns record of .jp or which root servers the cache server asked. would u help me where i can i find out those information ?
thx
category client { query_file; };
category unmatched { query_file; };
category queries { query_file; };
query file
=======
9-Mar-2006 18:33:28.896 client: debug 3: client 1.1.1.1#2716: UDP request
09-Mar-2006 18:33:28.897 client: debug 5: client 1.1.1.1#2716: using view '_default'
09-Mar-2006 18:33:28.910 client: debug 3: client 1.1.1.1#2716: query
09-Mar-2006 18:33:28.910 queries: info: client 1.1.1.1#2716: query: www.yahoo.co.jp IN MX +
09-Mar-2006 18:33:28.910 client: debug 10: client 1.1.1.1#2716: ns_client_attach: ref = 1
09-Mar-2006 18:33:28.911 client: debug 3: client 1.1.1.1#2716: replace
09-Mar-2006 18:33:28.912 client: debug 3: client @20cb18: udprecv
09-Mar-2006 18:33:29.983 client: debug 3: client 1.1.1.1#2716: send
09-Mar-2006 18:33:29.983 client: debug 3: client 1.1.1.1#2716: sendto
09-Mar-2006 18:33:29.983 client: debug 3: client 1.1.1.1#2716: senddone
09-Mar-2006 18:33:29.984 client: debug 3: client 1.1.1.1#2716: next
09-Mar-2006 18:33:29.984 client: debug 10: client 1.1.1.1#2716: ns_client_detach: ref = 0
09-Mar-2006 18:33:29.984 client: debug 3: client 1.1.1.1#2716: endrequest
category resolver { event_file; };
category network { event_file; };
category delegation-only { event_file; };
category lame-servers { event_file; };
event_file
========
09-Mar-2006 18:33:28.911 resolver: debug 1: createfetch: www.yahoo.co.jp MX
09-Mar-2006 18:33:28.911 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): create
09-Mar-2006 18:33:28.912 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): join
09-Mar-2006 18:33:28.912 resolver: debug 3: fetch 223918 (fctx 233d60(www.yahoo.co.jp/MX)): created
09-Mar-2006 18:33:28.912 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): start
09-Mar-2006 18:33:28.913 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): try
09-Mar-2006 18:33:28.913 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): cancelqueries
09-Mar-2006 18:33:28.913 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): getaddresses
09-Mar-2006 18:33:28.917 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): query
09-Mar-2006 18:33:28.917 resolver: debug 3: resquery 1ef868 (fctx 233d60(www.yahoo.co.jp/MX)): send
09-Mar-2006 18:33:28.917 resolver: debug 3: resquery 1ef868 (fctx 233d60(www.yahoo.co.jp/MX)): sent
09-Mar-2006 18:33:28.918 resolver: debug 3: resquery 1ef868 (fctx 233d60(www.yahoo.co.jp/MX)): senddone
09-Mar-2006 18:33:29.309 resolver: debug 3: resquery 1ef868 (fctx 233d60(www.yahoo.co.jp/MX)): response
09-Mar-2006 18:33:29.310 resolver: debug 10: received packet:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6760
;; flags: qr ; QUESTION: 1, ANSWER: 0, AUTHORITY: 5, ADDITIONAL: 10
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;www.yahoo.co.jp. IN MX
;; AUTHORITY SECTION:
jp. 172800 IN NS f.dns.jp.
jp. 172800 IN NS d.dns.jp.
jp. 172800 IN NS e.dns.jp.
jp. 172800 IN NS a.dns.jp.
jp. 172800 IN NS b.dns.jp.
;; ADDITIONAL SECTION:
f.dns.jp. 172800 IN A 150.100.2.3
f.dns.jp. 172800 IN AAAA 2001:2f8:0:100::153
d.dns.jp. 172800 IN A 210.138.175.244
d.dns.jp. 172800 IN AAAA 2001:240::53
e.dns.jp. 172800 IN A 192.50.43.53
e.dns.jp. 172800 IN AAAA 2001:200:0:1::4
a.dns.jp. 172800 IN A 203.119.1.1
a.dns.jp. 172800 IN AAAA 2001:dc4::1
b.dns.jp. 172800 IN A 202.12.30.131
09-Mar-2006 18:33:29.310 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): noanswer_response
09-Mar-2006 18:33:29.310 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): cache_message
09-Mar-2006 18:33:29.311 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): cancelquery
09-Mar-2006 18:33:29.311 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): cancelqueries
09-Mar-2006 18:33:29.314 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): try
09-Mar-2006 18:33:29.314 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): cancelqueries
09-Mar-2006 18:33:29.314 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): getaddresses
09-Mar-2006 18:33:29.316 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): query
09-Mar-2006 18:33:29.316 resolver: debug 3: resquery 1ef868 (fctx 233d60(www.yahoo.co.jp/MX)): send
09-Mar-2006 18:33:29.317 resolver: debug 3: resquery 1ef868 (fctx 233d60(www.yahoo.co.jp/MX)): sent
09-Mar-2006 18:33:29.317 resolver: debug 3: resquery 1ef868 (fctx 233d60(www.yahoo.co.jp/MX)): senddone
09-Mar-2006 18:33:29.775 resolver: debug 3: resquery 1ef868 (fctx 233d60(www.yahoo.co.jp/MX)): response
09-Mar-2006 18:33:29.776 resolver: debug 10: received packet:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36148
;; flags: qr ; QUESTION: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 3
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;www.yahoo.co.jp. IN MX
;; AUTHORITY SECTION:
yahoo.co.jp. 86400 IN NS ns10.yahoo.co.jp.
yahoo.co.jp. 86400 IN NS dnsg01.yahoo.co.jp.
;; ADDITIONAL SECTION:
ns10.yahoo.co.jp. 86400 IN A 210.80.243.9
dnsg01.yahoo.co.jp. 86400 IN A 211.14.12.10
09-Mar-2006 18:33:29.776 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): noanswer_response
09-Mar-2006 18:33:29.776 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): cache_message
09-Mar-2006 18:33:29.777 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): cancelquery
09-Mar-2006 18:33:29.777 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): cancelqueries
09-Mar-2006 18:33:29.778 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): try
09-Mar-2006 18:33:29.778 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): cancelqueries
09-Mar-2006 18:33:29.779 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): getaddresses
09-Mar-2006 18:33:29.779 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): query
09-Mar-2006 18:33:29.779 resolver: debug 3: resquery 1ef868 (fctx 233d60(www.yahoo.co.jp/MX)): send
09-Mar-2006 18:33:29.780 resolver: debug 3: resquery 1ef868 (fctx 233d60(www.yahoo.co.jp/MX)): sent
09-Mar-2006 18:33:29.780 resolver: debug 3: resquery 1ef868 (fctx 233d60(www.yahoo.co.jp/MX)): senddone
09-Mar-2006 18:33:29.980 resolver: debug 3: resquery 1ef868 (fctx 233d60(www.yahoo.co.jp/MX)): response
09-Mar-2006 18:33:29.980 resolver: debug 10: received packet:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18074
;; flags: qr aa ; QUESTION: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;www.yahoo.co.jp. IN MX
;; AUTHORITY SECTION:
yahoo.co.jp. 900 IN SOA yahoo.co.jp. postmaster.yahoo.co.jp. 2006030908 1800 900 86400 900
09-Mar-2006 18:33:29.981 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): noanswer_response
09-Mar-2006 18:33:29.981 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): ncache_message
09-Mar-2006 18:33:29.981 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): clone_results
09-Mar-2006 18:33:29.981 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): cancelquery
09-Mar-2006 18:33:29.981 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): done
09-Mar-2006 18:33:29.982 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): stopeverything
09-Mar-2006 18:33:29.982 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): cancelqueries
09-Mar-2006 18:33:29.982 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): sendevents
09-Mar-2006 18:33:29.982 resolver: debug 3: fetch 223918 (fctx 233d60(www.yahoo.co.jp/MX)): destroyfetch
09-Mar-2006 18:33:29.983 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): shutdown
09-Mar-2006 18:33:29.984 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): doshutdown
09-Mar-2006 18:33:29.984 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): stopeverything
09-Mar-2006 18:33:29.985 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): cancelqueries
09-Mar-2006 18:33:29.985 resolver: debug 3: fctx 233d60(www.yahoo.co.jp/MX'): destroy
-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On Behalf Of Barry Margolin
Sent: Thursday, March 09, 2006 1:16 PM
To: comp-protocols-dns-bind at isc.org
Subject: Re: Bind 9.3.2 - how do i know dns is using which root server
In article <duo8k6$e0e$1 at sf1.isc.org>,
"Alex Tang" <alextang at cms.hkcable.com> wrote:
> it is because our cache only dns was upgraded to 9.3.2 from bind 8, we want
> to find out that can it use the nearest root server to query ? We have a BGP
> session with a root server which is located in the local exchange. Therefore,
> we want to find out some log to show which root server will be use if the dns
> server need to query root server.
>
> otherwise we need to use sniffer or snoop to obtain those information.
BIND keeps track of the response times of servers that it has queried in
the past. When it needs to query a server for a particular zone, it
uses the one that had the best response time. So if you have a very
fast connection to one root server, it will usually be used.
You can enable debugging and it should log when it's querying outside
servers.
--
Barry Margolin, barmar at alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***
More information about the bind-users
mailing list