- To: evol@eskimo.com, calvin@eskimo.com
- Subject: Megapop Hosed DNS...
- From: Robert Dinse <nanook@eskimo.com>
- Date: Wed, 6 Jan 1999 15:34:08 -0800 (PST)
- cc: outages-list@eskimo.com
- Resent-Date: Wed, 6 Jan 1999 15:34:26 -0800
- Resent-From: outages-list@eskimo.com
- Resent-Message-ID: <"vYte13.0.xr4.1C_as"@mx1>
- Resent-Sender: outages-list-request@eskimo.com
- Prev by Date: IP Connectivity 12/27/98 8:25-8:30pm
- Next by Date: TIA1 crashed 1:15am 1/10/99
- Prev by thread: TIA1 crashed 1:15am 1/10/99
- Next by thread: IP Connectivity 12/27/98 8:25-8:30pm
- Index(es):
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Megapop Hosed DNS...
The DNS problems with the new addresses for the added MegaPOP capacity in
Seattle and Everett appear to not be a problem with MegaPOP/StarNet, but rather
a problem with ARIN. The ARIN whois database shows the address belonging to
StarNet, but the root name servers aren't pointing the inverse DNS to their
name servers (or to anywhere for that matter).
To fix this for however long it takes for that to be resolved; I've made
all of our name servers secondaries for 207.227.230 and 207.227.232, they allow
zone transfers from anywhere so this works.