- To: dns@megapop.net, support@megapop.net, noc@megapop.net, dave@megapop.net, outages-list@eskimo.com
- Subject: DNS Problems affecting POP/SMTP connections from Tampa/Minneapolis.
- From: Robert Dinse <nanook@eskimo.com>
- Date: Sat, 27 May 2000 23:02:13 -0700 (PDT)
- Newsgroups: lobby, announcements
- Resent-Date: Sat, 27 May 2000 23:02:22 -0700
- Resent-From: outages-list@eskimo.com
- Resent-Message-ID: <"P2_Hq.0.5u1.kPBCv"@mx1>
- Resent-Sender: outages-list-request@eskimo.com
- Prev by Date: Commerce 10:30PM 5/29 Maintenance Outage...
- Next by Date: commerce
- Prev by thread: Commerce 10:30PM 5/29 Maintenance Outage...
- Next by thread: commerce
- Index(es):
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
DNS Problems affecting POP/SMTP connections from Tampa/Minneapolis.
This is with respect to DNS problems which are sporadically preventing our
dial access customers from being able to connect to our POP and SMTP servers
from specific dial-up areas.
While I haven't seen a problem with Kansas since early friday, I am
continuing to see some problems with IP addresses for Tampa FL, and Minneapolis
MN POPs:
216.3.182.64 resolves to 02-066.033.popsite.net,
but 02-066.033.popsite.net resolves to 216.3.182.66.
I suspect 216.3.182.64 should resolve to 02-064.033.popsite.net.
192.216.54.64 resolves to 02-066.034.popsite.net,
but 02-066.034.popsite.net resolves to 192.216.54.66.
I suspect 192.216.54.64 should resolve to 02-064.034.popsite.net.
If you could fix these typo's it would be appreciated. The address
mismatch prevents our customers in those locations from being able to connect
to our POP and SMTP server (amoung others) when they are assigned those IP's.