- To: support@megapop.net, dave@megapop.net, outages-list@eskimo.com
- Subject: MegaPOP DNS Problems
- From: Robert Dinse <nanook@eskimo.com>
- Date: Thu, 17 Feb 2000 10:27:19 -0800 (PST)
- Resent-Date: Thu, 17 Feb 2000 10:27:49 -0800
- Resent-From: outages-list@eskimo.com
- Resent-Message-ID: <"qKQnk2.0.Hp3.as3hu"@mx1>
- Resent-Sender: outages-list-request@eskimo.com
- Prev by Date: Re: 56k/ISDN authentication, and routing; busies
- Next by Date: WWW
- Prev by thread: More Ports with BAD DNS...
- Next by thread: 56k/ISDN authentication, and routing; busies
- Index(es):
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
MegaPOP DNS Problems
There is a problem with DNS on some of the MegaPOP ports that causes
problems for our customers trying to connect to our servers.
For example, one of our customers connected and was assigned the IP
address of:
209.69.195.114
If I do an nslookup on that IP address I get:
Name: 15-114.008.popsite.net
Address: 209.69.195.114
So inverse DNS information exists, but if I turn around and do an nslookup
on the name that IP address resolved to:
*** eskimo.com can't find 15-114.008.popsite.net: Non-existent host/domain
There is no forward DNS on the name to match the inverse DNS.
Since we use the resolv+ resolver with the PARANOID option enabled on all
of our servers to prevent DNS spoofing, connections from ports with broken DNS
servers like this one are refused, which means our customers can't connect to
our servers.
The forward and inverse DNS information needs to be consistant with each
other.