Reverse DNS and Email Deliverability: How PTR Records Affect Your Inbox Placement
Missing or misconfigured reverse DNS (PTR records) cause email rejection at Gmail, Outlook, and Yahoo. Here's why rDNS matters and how to set it up correctly.
What is reverse DNS?
Reverse DNS maps an IP address back to a hostname using PTR records stored in in-addr.arpa. Forward DNS goes from hostname → IP; reverse DNS goes from IP → hostname.
For email, reverse DNS (rDNS) is used by receiving mail servers to verify that the sending server's IP address resolves to a meaningful hostname — and that hostname resolves back to the same IP. This bidirectional verification is called Forward-Confirmed reverse DNS (FCrDNS).
Why mail servers check PTR records
Spammers frequently send from dynamically assigned IPs, compromised residential connections, and cloud VMs with generic hostnames. These sources typically have either no PTR record or generic PTR records like '123-45-67-89.dynamic.isp.net'.
Legitimate mail servers are operated by organizations that control their IP space and set meaningful PTR records like mail.example.com. This is a basic signal of operational maturity that mail server operators use to quickly filter suspicious sources.
Gmail returns a 550 error for servers without valid PTR records. Outlook/Hotmail rejects email from IPs failing reverse DNS. Many corporate mail filters require FCrDNS.
How to set up a PTR record
PTR records are managed by whoever controls the IP address block — your hosting provider or ISP, not your domain registrar.
For dedicated servers and VPS: - DigitalOcean, Linode, Vultr, Hetzner: Set PTR in the server control panel under 'Reverse DNS' - AWS EC2: Request via AWS support - Azure: Set in the Public IP address configuration
For colocation or your own IP block: - Contact your upstream ISP to set PTR delegation - Then set PTR in your own DNS for your IP block
The PTR value should be your mail server hostname (e.g., mail.yourdomain.com), and that hostname must have an A record pointing back to the same IP.
PTR record setup by hosting provider
| Hosting Provider ↕ | Where to Set PTR ↕ | Steps ↕ |
|---|---|---|
| DigitalOcean | Droplet → Networking → PTR | Go to droplet settings → Networking tab → Reverse DNS → Enter hostname |
| Linode / Akamai | Linodes → IP Address → Reverse DNS | Click IP address in Linodes panel → Edit reverse DNS field |
| Vultr | Server → Settings → IPv4 → Reverse DNS | Select server → Settings → IPv4 → Click pencil icon next to IP |
| Hetzner Cloud | Server → Networking → IPv4 → Reverse DNS | Hetzner console → Server → Networking → Edit reverse DNS |
| AWS EC2 | AWS Support ticket required | EC2 does not allow self-service PTR changes — must submit request to AWS support with your EIP and desired hostname |
| Google Cloud (GCP) | VPC Network → IP addresses → Edit → DNS PTR record | GCP console → VPC Network → External IP addresses → pencil edit → PTR record field |
| Microsoft Azure | Public IP address → Configuration → Reverse FQDN | Azure portal → Public IP address resource → Configuration blade → Reverse FQDN |
| Shared hosting / cPanel | Not available — use host's mail server instead | Shared hosting IPs are managed by the provider; use your host's SMTP relay for outbound email |
Forward-Confirmed Reverse DNS (FCrDNS) is required
Setting a PTR record is not enough on its own. The PTR must point to a hostname (e.g., mail.yourdomain.com), and that hostname must have an A record that resolves back to the same IP address. This bidirectional verification — called FCrDNS — is what Gmail, Outlook, and Yahoo actually check. A PTR pointing to a hostname with no forward A record, or a forward A pointing to a different IP, both fail FCrDNS and will cause rejection.
Common PTR record mistakes
Generic PTR from hosting provider: Many cloud providers set a default PTR like 'ec2-1-2-3-4.compute-1.amazonaws.com'. This looks suspicious to mail servers. Override with your actual hostname.
PTR not matching HELO/EHLO: Your mail server announces itself with a hostname in the EHLO command. If this doesn't match the PTR (and both don't resolve to the same IP), you fail FCrDNS.
Forward DNS not configured: PTR points to mail.yourdomain.com but that hostname has no A record pointing back to the IP. This fails FCrDNS.
Multiple PTR records: An IP should have exactly one PTR record.
Check your domain's email health
Run a free scan against 60 blacklists. Validate SPF, DKIM, DMARC, and MX records in seconds.
Related free tools