Re: Strange internet case . . .

[Ken Sims <ken@xxxxxxxxx>]

Hi Jeff -

> > I would suspect a DNS problem or a routing problem.  I would use NSLOOKUP,
> > PING, and TRACERT from all three connection methods and compare the
> > results.  NSLOOKUP and PING should give the same results for all
> > three.  TRACERT will be different at the beginning, but should merge
> together.
>
>As of last night, it was fine.  Huh?

Actually, not real surprising.  Based on the results you gave in your other
message, it was obviously not a DNS problem.  (DNS problems can take a long
time to get fixed because often they only affect one domain or even just
one host in a domain.)

So most likely it was a routing problem.  Routing problems tend to get
fixed reasonably quickly because they have a lot more impact.  Certainly a
lot more people than just you were unable to reach the library's site.  And
it is possible that people at the library were unable to reach perhaps 1/3
of all domains.

Ken
http://www.ke9nr.org/
Opinions expressed are my own and do not necessarily represent the views of
my employer or anyone in their right mind.