Thanks for all your helps. The dig for version.bind and hostname.bind sometime works, sometime not. as you see:

pyh@dwdns153:~$ dig txt chaos version.bind @h.root-servers.net

; <<>> DiG 9.6.1-P2 <<>> txt chaos version.bind @h.root-servers.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21537
;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;version.bind.                  CH      TXT

;; ANSWER SECTION:
version.bind.           0       CH      TXT     "NSD 4.0.3"

;; Query time: 257 msec
;; SERVER: 128.63.2.53#53(128.63.2.53)
;; WHEN: Wed Apr 30 09:02:23 2014
;; MSG SIZE  rcvd: 52

pyh@dwdns153:~$ dig txt chaos hostname.bind @h.root-servers.net

; <<>> DiG 9.6.1-P2 <<>> txt chaos hostname.bind @h.root-servers.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29675
;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;hostname.bind.                 CH      TXT

;; ANSWER SECTION:
hostname.bind.          0       CH      TXT     "003.nzy.h.root-servers.org"

;; Query time: 256 msec
;; SERVER: 128.63.2.53#53(128.63.2.53)
;; WHEN: Wed Apr 30 09:02:37 2014
;; MSG SIZE  rcvd: 70

pyh@dwdns153:~$
pyh@dwdns153:~$
pyh@dwdns153:~$ dig txt chaos version.bind @h.root-servers.net +short

; <<>> DiG 9.6.1-P2 <<>> txt chaos version.bind @h.root-servers.net +short
;; global options: +cmd
;; connection timed out; no servers could be reached
pyh@dwdns153:~$
pyh@dwdns153:~$
pyh@dwdns153:~$ dig txt chaos version.bind @h.root-servers.net +short

; <<>> DiG 9.6.1-P2 <<>> txt chaos version.bind @h.root-servers.net +short
;; global options: +cmd
;; connection timed out; no servers could be reached


And this is the mtr info for h.root-servers.net:

pyh@dwdns153:~$ mtr h.root-servers.net --report
HOST: dwdns153.dns.yt.yygamedev.c Loss%   Snt   Last   Avg  Best  Wrst StDev
1. 113.108.228.129 40.0% 10 0.5 0.5 0.5 0.8 0.1 2. 121.14.46.93 10.0% 10 0.5 0.5 0.5 0.5 0.0 3. 121.14.37.33 0.0% 10 2.7 3.3 1.6 7.2 1.9 4. 121.14.37.6 0.0% 10 0.4 0.4 0.3 0.7 0.1 5. 121.14.50.13 0.0% 10 1.5 2.3 0.9 4.3 1.2 6. 113.108.208.97 0.0% 10 4.8 3.9 1.6 5.9 1.5 7. 202.97.34.202 0.0% 10 1.1 1.5 0.9 5.2 1.3 8. 202.97.61.234 0.0% 10 2.1 1.6 1.3 2.2 0.3 9. 202.97.52.154 0.0% 10 148.6 149.7 147.7 151.3 1.3 10. 202.97.49.158 0.0% 10 151.5 150.7 148.6 151.8 1.2 11. 218.30.54.198 0.0% 10 174.9 183.0 174.9 209.5 9.7 12. los-edge-05.inet.qwest.net 0.0% 10 169.8 175.9 169.8 180.5 3.4 13. 65-126-18-214.dia.static.qwe 0.0% 10 172.7 179.4 172.7 186.4 4.5 14. 143.56.244.2 0.0% 10 160.5 173.9 160.5 192.2 11.6 15. ap-1-1-1-nd.level3-lax.core. 0.0% 10 160.7 167.6 160.1 173.4 4.7 16. np-5-1-1-nd.sandiego.core.dr 0.0% 10 177.9 185.6 177.9 195.3 5.0 17. 138.18.190.89 10.0% 10 163.8 172.2 163.8 178.3 4.4 18. 138.18.190.114 10.0% 10 163.2 163.4 163.1 164.8 0.5 19. 128.63.2.53 10.0% 10 171.2 180.3 171.2 185.4 4.2

Regards.
Ken


于 2014-4-30 5:16, Warren Kumari 写道:
Oh, sure, I totally agree NSID/hostname.bind etc. will be very helpful.

My experience is that if these query hit a masquerading root node, you
mostly won't get an answer, by either no ANSWER section or empty string
in ANSWER section.

_______________________________________________
dns-operations mailing list
dns-operations@lists.dns-oarc.net
https://lists.dns-oarc.net/mailman/listinfo/dns-operations
dns-jobs mailing list
https://lists.dns-oarc.net/mailman/listinfo/dns-jobs

Reply via email to