Bill Jonas on Mon, 21 Oct 2002 20:39:09 -0400


[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PLUG] DNS Problem Now


On Mon, Oct 21, 2002 at 07:08:02PM -0400, Paul wrote:
> What would cause *all* DNS servers to have extremely long response times?

Well, the closeness of the IP addresses made me suspect that the two
machines are on the same network segment.  A traceroute confirmed this:

$ traceroute -f18 207.172.3.8
traceroute to 207.172.3.8 (207.172.3.8), 30 hops max, 38 byte packets
18  ge4-0.core2.lnh.md.rcn.net (207.172.15.18)  324.034 ms  325.896 ms 329.332 ms
19  pos5-0-0.core3.mrf.va.rcn.net (207.96.92.130)  338.086 ms  354.696 ms  355.453 ms
20  ge5-0-0.sys-core1a.mrf.va.rcn.net (208.59.255.85)  327.046 ms 336.568 ms  334.854 ms
21  corky.dns.rcn.net (207.172.3.141)  318.522 ms  338.460 ms  331.926 ms
$ traceroute -f18 207.172.3.9
traceroute to 207.172.3.9 (207.172.3.9), 30 hops max, 38 byte packets
18  ge4-0.core2.lnh.md.rcn.net (207.172.15.18)  350.408 ms  360.328 ms 320.479 ms
19  pos0-0-0.core3.mrf.va.rcn.net (208.59.94.74)  312.727 ms  327.534 ms 318.653 ms
20  ge5-0-0.sys-core1a.mrf.va.rcn.net (208.59.255.85)  317.359 ms 364.770 ms  336.711 ms
21  hellboy.dns.rcn.net (207.172.3.140)  352.516 ms  342.263 ms  352.258 ms

This, combined with the non-responsiveness to pings, suggests that they
were simply unreachable or experiencing packet loss during the time
period you had trouble with them.  Either that, or they're simply the
same machine, which might suggest that it was experiencing heavy load
during the time in question.

-- 
Bill Jonas    *    bill@billjonas.com    *    http://www.billjonas.com/
"They that can give up  essential  liberty to obtain a little temporary
safety deserve neither liberty nor safety."        -- Benjamin Franklin

Attachment: pgpsxZIfzD5UK.pgp
Description: PGP signature