What Is Reverse DNS (PTR) and Why Does Email Depend on It?

Forward DNS turns a name into an address. Reverse DNS does the opposite: give it 8.8.8.8 and it answers dns.google. The record that makes this work is called a PTR record, and it lives in a strange corner of DNS that most people never touch, right up until an email stops being delivered.

What is a PTR record?

A PTR record maps an IP address back to a hostname. It lives under a special zone, in-addr.arpa for IPv4 and ip6.arpa for IPv6, with the address written backwards. The reverse record for 8.8.8.8 is stored at 8.8.8.8.in-addr.arpa, which looks peculiar until you realise DNS reads right to left and the reversal makes delegation work the same way it does for ordinary names.

One important asymmetry: forward and reverse records are independent. Your A record can point example.com at an address while that address answers with a completely unrelated hostname, or with nothing at all. Nothing forces them to agree, which is exactly why mail servers check whether they do.

Why does email depend on this?

Receiving mail servers treat a missing or mismatched PTR record as a spam signal, and some reject on it outright. The logic is crude but effective: anyone who controls a block of addresses legitimately can set reverse DNS on it, and most spam comes from hijacked machines whose operators cannot.

The usual check is a forward-confirmed lookup. The server takes your sending IP, finds the PTR hostname, then looks that hostname back up and checks it resolves to the same address. Both directions have to agree. A PTR that points at mail.yourdomain.com is worthless if mail.yourdomain.com resolves somewhere else.

Who controls your reverse DNS?

Not you, usually, and this catches people out. PTR records are delegated by whoever owns the address block, which means your ISP, your hosting provider or your cloud platform. You can publish any forward record you like for a domain you own, but you cannot publish a PTR for an address you merely rent.

What you do instead depends on the provider. Most hosting and cloud panels have a field for it, sometimes labelled rDNS. Residential connections almost never let you change it, which is one of several reasons running a mail server from home goes badly.

What does a residential reverse record look like?

Something like this, varying by provider:

broadband-203-0-113-45.example-isp.net

Generic, auto-generated, with the address embedded in the name. Mail servers read that pattern as a consumer connection and weight it accordingly. A business connection or a hosted server usually gets either a blank record or one you can set yourself.

When is reverse DNS useful beyond mail?

• Reading logs. A column of raw addresses tells you nothing; resolved hostnames tell you which are crawlers, which are cloud providers and which are home connections.
• Verifying a crawler. Google, Bing and others document a reverse-then-forward check as the correct way to confirm a bot is genuine rather than someone spoofing the user agent. The claimed name has to resolve back to the same address.
• Identifying infrastructure. Reverse names frequently leak the provider, the data centre and sometimes the service, which is fast reconnaissance when you are tracing a route or an abuse report.

Why does a lookup return nothing?

An empty result is normal and is not an error. Most addresses on the internet have no PTR record, because nobody bothered to set one. You will also see a genuine absence where the provider delegated the block but never populated it, and occasionally a stale record left behind by a previous tenant of the address, which is its own small embarrassment when the old company name shows up in your logs.

If you are chasing a mail delivery problem and the lookup comes back empty, that is your answer, and the fix is a support ticket to whoever owns the address.

Checking an address

Put any IPv4 or IPv6 address into the reverse DNS lookup to see its PTR record and hostname. If you want the other direction, the DNS lookup resolves names to addresses, and the IP lookup adds the network owner and ASN, which is often the detail you actually wanted. For the wider picture of which record does what, DNS records explained covers the set.