Reverse DNS (PTR) Records: What They Are and Why Mail Servers Care

Most DNS records answer "what's the IP for this name." A PTR record answers the opposite question: "what's the name for this IP." It's a small piece of the DNS system that matters far more than its simplicity suggests — particularly for email.

How reverse DNS actually works

Forward DNS and reverse DNS are separate systems that happen to share the same protocol. A PTR record lives in a special reverse zone — for IPv4, under in-addr.arpa, with the IP address octets reversed (looking up 203.0.113.10 means querying 10.113.0.203.in-addr.arpa). Critically, the owner of a domain does not control its own PTR records — the owner of the IP address block does, which in most cases is your hosting provider or ISP, not you. This is the single most common point of confusion: you can't fix a broken PTR record in your own DNS provider's dashboard, because it isn't your zone to edit.

Why mail servers check it specifically

When a receiving mail server gets a connection from an IP, many will perform a reverse DNS lookup on that IP, then a forward lookup on the hostname it gets back, and check that the forward lookup resolves back to the same IP (a check sometimes called "FCrDNS," forward-confirmed reverse DNS). An IP with no PTR record at all, or one that doesn't resolve back consistently, is treated as a signal of a poorly-configured or potentially abusive sender — residential and dynamic IP ranges typically have no legitimate PTR set up, which is part of why sending mail directly from a home connection is reliably rejected.

Beyond the technical check, a PTR record that reads like a generic hosting-provider default (something like host-203-0-113-10.example-hosting.net) rather than a hostname related to your actual mail domain is also a mild reputation signal, even where it doesn't cause outright rejection.

How to check yours

Look up the sending IP for your mail server — DNSDecode's IP intelligence shows the current reverse DNS result directly, alongside the organisation and ASN that IP belongs to, which is usually enough to identify who to contact if it needs changing.

How to fix a missing or wrong PTR record

1. Identify who controls the IP. The ASN/organisation shown in an IP lookup tells you who owns the address block — usually your VPS or hosting provider, sometimes your ISP for a dedicated connection.
2. Request the change through them, not your DNS provider. Most VPS and cloud hosting providers offer this as a self-service option in their control panel (often labelled "reverse DNS" or "PTR record"); some require a support ticket.
3. Point it at your actual mail hostname — the same hostname your server identifies itself as in the SMTP HELO/EHLO greeting, for consistency.
4. Verify the forward match too. The hostname the PTR record points to should itself have an A record resolving back to the same IP, completing the FCrDNS loop.

It's a small, easily overlooked piece of infrastructure — but for a domain sending its own mail, it's worth getting right alongside SPF, DKIM, and DMARC (see our full email authentication guide).