Reverse DNS Lookup

What is Reverse DNS?

Reverse DNS (rDNS) is the process of resolving an IP address back to a hostname. While regular (forward) DNS maps a hostname like mail.example.com to an IP address, reverse DNS does the opposite — it maps an IP address like 93.184.216.34 back to its associated hostname. This mapping is stored as a PTR (pointer) record in the DNS system.

How Reverse DNS Works

For IPv4 addresses, reverse DNS uses a special DNS zone called in-addr.arpa. The IP address digits are reversed and this suffix is appended. For example, to look up the PTR record for 8.8.8.8, the DNS query is made for 8.8.8.8.in-addr.arpa. This reversed notation exists because DNS hierarchies flow left-to-right (from general to specific), but IP addresses are read with the most general part (the network) on the left.

For IPv6 addresses, the process is similar but uses the ip6.arpa zone. Each nibble (4-bit group) of the full 128-bit IPv6 address is reversed individually and separated by dots. For example, 2001:db8::1 becomes a 32-character reversed nibble sequence followed by .ip6.arpa.

Why Reverse DNS Matters

• Email Deliverability — Mail servers check PTR records when receiving email. If your mail server's IP doesn't have a PTR record, or if the hostname doesn't match (no forward-confirmed reverse DNS, or FCrDNS), your emails are far more likely to be marked as spam or rejected outright. Major providers like Gmail, Outlook, and Yahoo all use PTR record validation.
• Spam Filtering — IP-based spam filters use reverse DNS as one of their key signals. IPs without valid PTR records are treated with suspicion by spam detection systems like SpamAssassin.
• Network Troubleshooting — When analyzing logs (web server logs, firewall logs), hostnames are far more informative than bare IP addresses. Network tools like traceroute and ping perform reverse DNS lookups to show human-readable names for each hop.
• Security Auditing — Security professionals use reverse DNS to identify the owner or purpose of an IP address making connections to their systems.
• CDN and Cloud Verification — Services often verify that the client's IP reverse-resolves to a specific domain to confirm the request comes from a legitimate source.

PTR Record Requirements

Only the owner of an IP block can set PTR records — unlike A or CNAME records which are controlled by the domain owner, PTR records are managed by whoever controls the IP block (typically your ISP or hosting provider). If you run a mail server, you'll need to ask your hosting provider to set a PTR record for your IP pointing to your mail server's hostname.

Forward-Confirmed Reverse DNS (FCrDNS)

A best practice for email servers is to have forward-confirmed reverse DNS, also called fully-qualified reverse DNS. This means the PTR record for your IP resolves to a hostname, AND that hostname's A record resolves back to the same IP. This double verification provides strong proof that the IP and hostname are legitimately associated, and is a requirement for many strict mail server configurations.

Common PTR Record Formats

ISPs and hosting providers often set PTR records automatically with a generic format like pool-72-71-234-56.dllstx.fios.verizon.net or ec2-54-239-20-1.compute-1.amazonaws.com. Custom PTR records for dedicated servers are usually set to match the server's hostname, like mail.yourdomain.com.