[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Seattle 56k / E-mail problems
- To: outages-list@eskimo.com
- Subject: Seattle 56k / E-mail problems
- From: Robert Dinse <nanook@eskimo.com>
- Date: Thu, 27 Jul 2000 10:49:05 -0700 (PDT)
- Newsgroups: lobby, announcements
- Resent-Date: Thu, 27 Jul 2000 10:49:18 -0700
- Resent-From: outages-list@eskimo.com
- Resent-Message-ID: <"893_k2.0.6j4.UO7Wv"@mx1>
- Resent-Sender: outages-list-request@eskimo.com
There is a problem with StarNet/MegaPOP's inverse DNS on an address
block used for the Seattle/Tacoma/Everett POP:
64.24.128.xxx #009-Seattle/Everett/Tacoma, WA
64.24.129.xxx #009-Seattle/Everett/Tacoma, WA
64.24.130.xxx #009-Seattle/Everett/Tacoma, WA
64.24.131.xxx #009-Seattle/Everett/Tacoma, WA
64.24.132.xxx #009-Seattle/Everett/Tacoma, WA
64.24.133.xxx #009-Seattle/Everett/Tacoma, WA
That is causing problems for customers trying to use our SMTP mail server,
ftp server, and other servers that require proper inverse DNS.
The ARIN database shows the following name servers providing inverse
DNS mapping for these addresses:
Netname: STARNET-CIDR-BLK-2
Netblock: 64.24.0.0 - 64.24.191.255
Maintainer: STNI
Coordinator:
Parker, Chris (CP178-ARIN) noc@starnetusa.net
847-963-0116
Domain System inverse mapping provided by:
EMAIL.STARNETINC.COM 204.178.185.5
NS.STARNETINC.COM 204.178.185.105
However, if you query these servers for inverse DNS information for these
IP addresses, they fail:
> server 204.178.185.5
Default Server: old-ns0.starnetinc.com
Address: 204.178.185.5
> 64.24.35.110
Server: old-ns0.starnetinc.com
Address: 204.178.185.5
*** old-ns0.starnetinc.com can't find 64.24.35.110: Non-existent host/domain
As a result, our customers using 56k/ISDN in Seattle/Tacoma/Everett can
not connect to our SMTP server, FTP server, or some other servers if they are
assigned one of these IP addresses when they connect.