-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Andy Green wrote:
| Hey Brian, can you give us an example domain that you experienced the | problem with, and I guess that way we can see if it is the DNS for that | domain that is struggling, or infer that it is your upstream DNS | provider's server that is slow.
I reviewed the thread and see the first post has some addresses.
I get the nameserver addresses from whois.
# dig @ns2.osdn.com hardware.slashdot.org
; <<>> DiG 9.2.5 <<>> @ns2.osdn.com hardware.slashdot.org ; (1 server found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27430 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 5, ADDITIONAL: 5
;; QUESTION SECTION: ;hardware.slashdot.org. IN A
;; ANSWER SECTION: hardware.slashdot.org. 7200 IN A 66.35.250.151
;; AUTHORITY SECTION: slashdot.org. 7200 IN NS ns2.osdn.com. slashdot.org. 7200 IN NS ns2.vasoftware.com. slashdot.org. 7200 IN NS ns3.vasoftware.com. slashdot.org. 7200 IN NS ns1.osdn.com. slashdot.org. 7200 IN NS ns1.vasoftware.com.
;; ADDITIONAL SECTION: ns1.osdn.com. 7200 IN A 66.35.250.10 ns1.vasoftware.com. 72924 IN A 12.152.184.135 ns2.osdn.com. 7200 IN A 66.35.250.11 ns2.vasoftware.com. 72924 IN A 12.152.184.136 ns3.vasoftware.com. 72924 IN A 66.35.250.12
;; Query time: 164 msec ;; SERVER: 66.35.250.11#53(66.35.250.11) ;; WHEN: Thu Apr 7 12:12:41 2005 ;; MSG SIZE rcvd: 244
# dig @ns1.tmpw.net jobsearch.monster.com
; <<>> DiG 9.2.5 <<>> @ns1.tmpw.net jobsearch.monster.com ; (1 server found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4501 ;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION: ;jobsearch.monster.com. IN A
;; ANSWER SECTION: jobsearch.monster.com. 600 IN A 63.112.169.3 jobsearch.monster.com. 600 IN A 63.121.29.3
;; AUTHORITY SECTION: monster.com. 4800 IN NS ns1.tmpw.net. monster.com. 4800 IN NS ns2.tmpw.net.
;; ADDITIONAL SECTION: ns1.tmpw.net. 3600 IN A 63.121.28.53 ns2.tmpw.net. 3600 IN A 63.112.168.53
;; Query time: 118 msec ;; SERVER: 63.121.28.53#53(63.121.28.53) ;; WHEN: Thu Apr 7 12:14:45 2005 ;; MSG SIZE rcvd: 147
After this somewhat unscientific and one-shot test I continue to suspect the problem is with the performance of his upstream DNS, or some communication problem that can lose packets including his DNS ones, since the servers are both responding in well below 200ms.
- -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFCVRaDjKeDCxMJCTIRArs7AJ48UCultq6qLrRPWVJ2GnsTZqNFIgCeKCsr qexzTT6aTJ/rsMeRy53K0To= =Bwi3 -----END PGP SIGNATURE-----
