Reverse DNS Lookup

What reverse DNS actually is

Forward DNS maps a name to an address. Reverse DNS does the opposite through a PTR record, published in a special zone: in-addr.arpa for IPv4 and ip6.arpa for IPv6. Crucially, the PTR record is controlled by whoever owns the IP address block, not by whoever owns the domain name. That is why you configure reverse DNS with your hosting provider rather than in your own DNS panel.

Why mail servers care

A large share of receiving mail servers check that a sending IP has a PTR record and that the hostname it returns resolves forward to the same IP. This is forward-confirmed reverse DNS, and failing it is one of the most common reasons legitimate mail lands in spam or is rejected outright. Any server sending mail directly needs a matching PTR, and the hostname should be a real name in a domain you control, not the provider's generic pattern.

Verifying a crawler

Reverse DNS is how you confirm a bot is genuine. A request claiming to be Googlebot proves nothing, since the user-agent string is trivially forged. The correct check is reverse-then-forward: look up the connecting IP, confirm the hostname ends in googlebot.com or google.com, then resolve that hostname forward and confirm it matches the original IP. Checking only the reverse direction is insufficient, because an attacker who controls their own reverse zone can put any name there.

Absence is normal

Most residential and mobile addresses have either no PTR or a generic one assigned by the ISP. That is unremarkable and says nothing about the user. Reverse DNS is informative for servers and near-meaningless for consumer connections.

One address, one name

Unlike forward DNS, where many names can point at one address, reverse convention expects a single PTR per address. Multiple PTR records are legal but handled inconsistently and are best avoided.