We are in configuring Mail Server and we would like to add a PTR record to our DNS aim against Spam Scope. So please kindly help to guide us to do adding this record.
In case it helps others in a similar situation: I have just discovered that PTR (and so reverse DNS) records are specified at the IP block, not the domain. That makes sense, of course, since the PTR record points to a domain from an IP, rather than the other way around.
Apparently my server host (who own the IP) should be able to add the PTR record for me.
I'm not having issues with Gmail for the time being, so I'm going to just leave things as they are. But if I hit any more problems I'll see about getting the PTR record added at my host and will report back here.
Add me to the list of those who run mail servers on domains using Dynadot to manage DNS. We need PTR records. Mail is getting silently dropped from a widening variety of destinations.
Just to update everyone on my post from over a year ago: I did get this sorted properly, with PTR records, by asking my server host (Linode) to add them. So if anyone is in the same boat - ask whoever hosts your server for help. I don't think there's anything that Dynadot can do here at all, even theoretically (though it would be nice if one of their technical staff would confirm).
We appreciate your help tips and do apologize for the inconvenience. I will suggest our team the PTR adding feature. Again, thanks for sharing your skills.
Thanks for all the attention on this issue. We have contacted our engineer team and looks like the PTR record has to be provided by the company that supplies the IP address for the customer. That is to say, if you are using third party hosting, you could still set other DNS records with Dynadot but for the PTR record, it will still need to be done with the hosting's side. If you use Dynadot VPS, we can provide a PTR record with the ip address you need to set it up for.
Not only Gmail and AOL, but an ISP you may have heard of, Comcast, bounces email for lack of a PTR record:
---------------- 554 - [PTR lookup failure] Comcast requires all sending mail server IP addresses have a valid PTR record set up. This error results when the lookup failed.
NXDOMAIN response. One of the authoritative servers for the relevant section of the in-addr.arpa DNS tree is saying that there is no PTR record for the given IP address.
Looks like you are using a third party name server. The PTR record needs to be set up from the hosting's side. You may want to contact them to see where the issue is.