- To: outages-list@eskimo.com
- Subject: Western Washington
- From: Robert Dinse <nanook@eskimo.com>
- Date: Thu, 12 Oct 2000 19:06:29 -0700 (PDT)
- Newsgroups: lobby, announcements
- Resent-Date: Thu, 12 Oct 2000 19:06:44 -0700
- Resent-From: outages-list@eskimo.com
- Resent-Message-ID: <"lCfqF2.0.Vp5.pucvv"@mx1>
- Resent-Sender: outages-list-request@eskimo.com
- Prev by Date: Eskimo.Com Crash
- Next by Date: Megapop Authentication Problems
- Prev by thread: Megapop Authentication Problems
- Next by thread: Eskimo.Com Crash
- Index(es):
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Western Washington
We had some problems last night and today with the access numbers that
were servied out of the Seattle2 POP.
The name servers that were assigned via DHCP, that is those that your
system will get automatically if you don't specify DNS servers manually, were
not responding to dial-up customers queries.
This was very strange since we could query them from here fine, and if
customers configured to use the name servers we specify, and they had a
non-broken version of dial-up networking that didn't ignore those settings,
things would work OK for them so it didn't seem like a general routing problem.
It turned out after much teeth gnashing and hair pulling that a faulty
router in Oakland through which traffic to the Seattle2 POP was to blame.
This also affected San Francisco, Stockton, and Oakland POPs.
The router has been repaired as of 13:34 (1:34 PM) Pacific time.