Reverse DNS and PTR records explained

The short version

A reverse-DNS lookup asks for a PTR record. For IPv4, the address is reversed beneath in-addr.arpa. IPv6 reverse DNS uses the ip6.arpa tree.

If a PTR record exists, it can return a hostname such as a mail-server or provider hostname. If no PTR exists, the lookup simply has no useful name to return.

Forward DNS and reverse DNS are separate

An A or AAAA record is controlled through the DNS zone for a hostname. A PTR record is normally controlled by whoever manages the IP address range, which is often an ISP, cloud provider or hosting company.

Creating mail.example.com -> 203.0.113.10 does not automatically create the reverse mapping 203.0.113.10 -> mail.example.com.

Why reverse DNS matters for email

Receiving mail systems often use reverse DNS as one signal when evaluating an SMTP server. A sensible PTR record, especially one that resolves forward again to the sending address, can help show that the server is deliberately configured rather than an anonymous endpoint.

Reverse DNS is not a replacement for SPF, DKIM or DMARC, and a valid PTR does not guarantee mail delivery. It is one part of a larger reputation and authentication picture.

What is forward-confirmed reverse DNS?

A common consistency check is to take the hostname returned by PTR and resolve that hostname forward again. If one of the resulting addresses matches the original IP, the forward and reverse mappings are consistent.

This is often called forward-confirmed reverse DNS. It is useful, but it still does not prove who operates a service or whether traffic should be trusted.

Why an IP might have no PTR record

PTR records are optional for most ordinary internet use. Residential connections, temporary cloud addresses and many client networks may have generic PTR names or none at all. A missing PTR is therefore normal in many contexts.