Reverse DNS entries for MX records

[thisisit3]

I've just started playing with my new vps account.

One thing i noticed is that the DNS Report at dnsstuff.com says that i haven't got reverse DNS entries for MX records. The complete message is as follows:

"ERROR: The IP of one or more of your mail server(s) have no reverse DNS (PTR) entries. RFC1912 2.1 says you should have a reverse DNS for all your mail servers. It is strongly urged that you have them, as many mailservers will not accept mail from mailservers with no reverse DNS entry. You can double-check using the 'Reverse DNS Lookup' tool at the DNSstuff site if you recently changed your reverse DNS entry (it contacts your servers in real time; the reverse DNS lookups in the DNS report use our local caching DNS server)."

Any ideas how to fix this problem? i'm not a DNS expert but it seems like an important error.

[JPC-Masood]

Please open a support ticket and provide them the IP and hostname that you want for it for reverse record.

[JPC-Masood]

As a side note this error message on the dnsstuff site is wrong for unique IP web sites, because the sending mail server does not use that IP in a shared environment, hence the RFC they refer to does not apply to that situation.

[thisisit3]

Thanks masood, i've opened a ticket.

[Ron]

As a side note this error message on the dnsstuff site is wrong for unique IP web sites, because the sending mail server does not use that IP in a shared environment, hence the RFC they refer to does not apply to that situation.

Could a reverse record be created for a domain on a shared server with a unique IP pointing to the shared IP of the mailserver?

Just wondering.

[JPC-Masood]

Yes, sure. Any IP can have a reverse dns.

[thisisit3]

Not very flexible as it is. Since cpanel/whm doesn't do it automaticaly, we'd have to open a ticket for every single resold domain.

[JPC-Masood]

Not very flexible as it is. Since cpanel/whm doesn't do it automaticaly, we'd have to open a ticket for every single resold domain.

Only if that resold account:

1) is setup on a unique IP
2) and you want to remove that annoying message from DNSstuff

Otherwise there is absolutely no need for it except the main IP of the VPS or Server.

[thisisit3]

Indeed i see that now.

I've setup a reverse record for my main shared IP, so all the domains without a dedicated IP pass all tests.

but, what happens with domains with dedicated IPs? is that error important enough to actualy open tickets for all those domains? or should we just ignore it?

[JPC-Masood]

I have not seen any real problem with it so I normally ignore it.