What Is Reverse DNS and Why PTR Records Matter
Reverse DNS maps an IP address back to a hostname. The record type is PTR, and it is commonly used for mail server reputation, logs, abuse handling and infrastructure identification.
Forward DNS versus reverse DNS
A and AAAA records are managed in the domain zone and map names to IP addresses. PTR records live in reverse zones controlled by the owner of the IP range.
That is why changing example.com at your DNS provider usually does not change the PTR for a server IP.
dig example.com A +short
dig -x 203.0.113.10 +shortForward-confirmed reverse DNS
For mail servers, a common check is whether the PTR hostname resolves back to the sending IP. This does not replace SPF, DKIM or DMARC, but it is a useful reputation signal.
dig -x 203.0.113.10 +short
dig mail.example.com A +shortWhere PTR is configured
- In cloud hosting, PTR is usually configured in the provider control panel.
- For dedicated servers, the data center or network provider controls the reverse zone.
- IPv4 reverse zones use in-addr.arpa.
- IPv6 reverse zones use ip6.arpa.
- A missing PTR does not stop IP connectivity, but it can hurt email delivery.
Common PTR mistakes
Adding PTR to the normal domain zone
Resolvers look for PTR in the reverse DNS hierarchy, not beside the A record.
Using a generic provider hostname
A clear hostname aligned with the service is usually better for operations and mail.
Forgetting the forward check
The PTR name should normally resolve back to the same IP for mail use.
Expecting instant changes
Recursive resolvers may cache old PTR or NXDOMAIN answers until TTL expires.