Reverse DNS Lookup (PTR)

Finds the hostname associated with an IP address — the reverse of a normal A record lookup. Query it directly, or it happens automatically whenever traceroute or a mail server tries to resolve an IP back to a name.

What's actually happening

A PTR record maps an IP address back to a hostname, stored in the special in-addr.arpa zone for IPv4 (ip6.arpa for IPv6). The important detail: it's managed by whoever owns the IP block — usually your hosting provider or ISP — not by whoever owns the domain the hostname points at. That's why you often can't just set a PTR record yourself; it goes through a support ticket or a control panel your provider exposes for exactly this purpose.

Why this matters more than it looks like it should

• Email deliverability — most receiving mail servers reject or heavily penalise mail from an IP with no PTR record at all. If you're running your own mail server, this isn't optional.
• Security investigations — a quick way to identify which organisation actually owns a suspicious IP, before digging further
• Readable traceroutes — hop-by-hop output with hostnames attached is a lot easier to reason about than a column of raw IPs
• Log readability — access logs with resolved hostnames tell you more at a glance than the IP alone, though resolving on the fly for every log line has its own performance cost worth being aware of

If you're setting up a mail server and email keeps getting flagged as spam despite correct SPF/DKIM/DMARC, a missing or mismatched PTR record is one of the first things worth checking — it's an easy thing to overlook because it lives with your IP provider, not your DNS provider, and the two aren't always the same conversation.