-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
When I am querying for a hostname for the ip-address 213.201.233.108
there is a huge difference between dig and dnsq:
$ dnsq ptr 108.233.201.213.in-addr.arpa 213.201.128.21
12 108.233.201.213.in-addr.arpa:
temporary failure
takes 11 seconds, whereas:
$ dig ptr 108.233.201.213.in-addr.arpa @213.201.128.21
; <<>> DiG 9.2.4 <<>> ptr 108.233.201.213.in-addr.arpa @213.201.128.21
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 12902
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;108.233.201.213.in-addr.arpa. IN PTR
;; Query time: 41 msec
;; SERVER: 213.201.128.21#53(213.201.128.21)
;; WHEN: Mon Jan 15 11:25:06 2007
;; MSG SIZE rcvd: 46
takes only 0.2s
The question is, why does it take so long for dnsq to fail? If it works
as designed, what is the design?
Thanks,
Ben Mesman.
Additional info:
I got the nameserver using:
$ dnsq ns 108.233.201.213.in-addr.arpa 127.0.0.1
2 108.233.201.213.in-addr.arpa:
159 bytes, 1+0+3+3 records, response, weird ra, noerror
query: 2 108.233.201.213.in-addr.arpa
authority: 233.201.213.in-addr.arpa 164507 NS ns1.novaxess.nl
authority: 233.201.213.in-addr.arpa 164507 NS ns2.novaxess.nl
authority: 233.201.213.in-addr.arpa 164507 NS ns3.novaxess.nl
additional: ns1.novaxess.nl 78107 A 213.201.128.21
additional: ns2.novaxess.nl 78107 A 213.201.191.18
additional: ns3.novaxess.nl 78107 A 213.239.156.38
Querying any of the other nameservers for the PTR-record shows the same
"problem".
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFq19hyBtfMQraccIRAtLeAJ9LPwibrNfMa7Ey1nWIWGh1J7yslgCeK0yF
nYT+5pVPp9CYdqze8jHnJMU=
=KKFu
-----END PGP SIGNATURE-----
|