Question

[Mark_Andrews at isc.org]

	Well it helps if the listed nameservers actually respond to
	DNS queries.  It also helps if you don't have perform multiple
	traversals from the roots to find the addresses of nameservers.

	People wonder why the DNS is slow.  Usually is is because they
	create complicated and/or broken setups.

	Mark

forums.ws.              21600   IN      NS      ip33-167.tor.istop.com.
forums.ws.              21600   IN      NS      ip34-167.tor.istop.com.
;; Received 118 bytes from 216.35.187.250#53(NS2.DNS.ws) in 833 ms

forums.ws.              86400   IN      A       66.11.167.33
forums.ws.              3600    IN      NS      ip33-167.tor.istop.com.
;; Received 79 bytes from 66.11.167.33#53(ip33-167.tor.istop.com) in 293 ms


% ping ip34-167.tor.istop.com
PING ip34-167.tor.istop.com (66.11.167.34): 56 data bytes
64 bytes from 66.11.167.34: icmp_seq=0 ttl=47 time=294.590 ms
64 bytes from 66.11.167.34: icmp_seq=1 ttl=47 time=294.604 ms
64 bytes from 66.11.167.34: icmp_seq=2 ttl=47 time=293.167 ms
^C
--- ip34-167.tor.istop.com ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 293.167/294.120/294.604/0.674 ms
% dig forums.ws @ip34-167.tor.istop.com

; <<>> DiG 8.3 <<>> forums.ws @ip34-167.tor.istop.com 
; (1 server found)
;; res options: init recurs defnam dnsrch
;; res_nsend to server ip34-167.tor.istop.com  66.11.167.34: Operation timed out
% ping ip34-167.tor.istop.com
PING ip34-167.tor.istop.com (66.11.167.34): 56 data bytes
64 bytes from 66.11.167.34: icmp_seq=0 ttl=47 time=316.281 ms
64 bytes from 66.11.167.34: icmp_seq=1 ttl=47 time=308.558 ms
^C
--- ip34-167.tor.istop.com ping statistics ---
3 packets transmitted, 2 packets received, 33% packet loss
round-trip min/avg/max/stddev = 308.558/312.419/316.281/3.862 ms
%


--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at isc.org