On Wed, 16 Jun 2004 13:03:19 -0700, LRW wrote:
> We send out monthly e-mails to our customers, and I've just noticed we get
> a few replies back from domains saying they're refusing e-mail from
> ourserver because we don't have a reverse DNS.
>
> Now, I don't know what that means. We lease our own server from
> rackspace.com, but before I go to them I wanted to find out more about the
> issue itself, and if there's anything I can do on my end before I go to
> them with it.
>
> I did a newsgroup search, but all I could find are posts WAY over my head
> regarding RFC's and other things.
>
> Can someone point me to something that explains what a no reverse DNS
> error indicates and how to take care of it?
It means that there is no address-to-name (PTR) record in the Internet DNS
for your server's IP address. It is the responsibility of whoever the
relevant in-addr.arpa domain is delegated to to add this. Usually this is
the organisation owning the enclosing /24 or larger subnet. From what you
say, it clearly isn't you.
When you leased your server, did you get the IP address with it? If so
contact the leasing company. If not, contact whoever gave you the IP
address. It's best to have the PTR and A records matching - i.e. if I
look up your IP address and get "your.server.com" back, then look up
"your.server.com" I should get the same IP address back. But usually this
isn't critical, it is just the presence of an address-to-name mapping
which the other servers care about.
We find we have to accept mail from servers with misconfigured or missing
DNS but we do a lot of business in South East Asia where things are often
set up rather badly.
> PS: I tried comp.protocols.dns.bind 1st, but they're moderated and only
> accept messages from subscribers.
Do they? Last time I posted to it it was OK. It's moderated, but the
moderators pass all relevant messages, or at least they used to. Maybe
it's changed as it's been a few months since I posted to it. Certainly I
can't see your post there.
> If there's a more appropriate forum
> for this message, please let me know. Thanks
There's comp.protocols.tcp-ip.domains but that's fairly low traffic.
Personally I think this NG is OK but not everyone may agree. After all
many people run their nameservers on Linux - I do.
To see the PTR record for an IP address use:
dig -x <ip address>
PS if you're talking about celticbear.com that does have a PTR, although
it points to blue.dnspages.net. However, this in turn points back at the
same IP so this is OK.
Regards, Ian
|
Similar Threads
Linear Mode
