Reverse DNS (rDNS) & PTR Records: The Ultimate Deliverability Guide

1. What is Reverse DNS (rDNS) and PTR?

In standard (forward) DNS, when your computer needs to access a server, it looks up an A record to translate a human-readable domain name into an IP address. Reverse DNS (rDNS) performs the exact opposite operation: given an IP address, it queries DNS to uncover the registered domain name associated with that host.

This is accomplished using a specialized DNS record type known as a Pointer (PTR) record, which lives within special top-level reverse mapping zones: .in-addr.arpa for IPv4 addresses and .ip6.arpa for IPv6 addresses.

2. Why Gmail, Outlook & Yahoo Mandate rDNS

In the early days of the internet, spammers utilized residential broadband connections, compromised IoT devices, and infected home PCs to blast spam directly into corporate mailboxes. These residential connections typically carry generic PTR records like c-98-210-33-12.hsd1.ca.comcast.net or have no reverse DNS at all.

To combat this, major email receivers instituted a zero-tolerance policy: any mail server connecting to their port 25 without a valid, non-generic PTR record is immediately rejected with a 550 permanent error.

3. Forward-Confirmed Reverse DNS (FCrDNS) Explained

Having a PTR record alone is not enough; it must satisfy Forward-Confirmed Reverse DNS (FCrDNS). Here is the verification process receiving MTAs run in real time:

1. Connection established from IP: 198.51.100.50.
2. Receiver executes reverse lookup for 50.100.51.198.in-addr.arpa -> Returns PTR: mail.yourbrand.com.
3. Receiver executes forward lookup for mail.yourbrand.com -> Returns A record: 198.51.100.50.
4. Verification Passed: Because the forward lookup matches the connecting IP, the identity of the sending server is authenticated.

4. The Golden Rule: Matching EHLO with PTR

When an SMTP connection opens, the sender presents itself using the EHLO (Extended Hello) command:

EHLO mail.yourbrand.com
        

The hostname provided in the EHLO command must exactly match the PTR record assigned to that IP. A discrepancy between your EHLO greeting and your PTR record is one of the highest weighted spam signals in Apache SpamAssassin, Gmail Spam Filter, and Spamhaus detection algorithms.

5. Setting PTR on Major Cloud Hosts (AWS, Hetzner, DO)

Because PTR records are tied to the IP subnet, you configure them within your cloud server control panel:

• Hetzner: Cloud Console -> Select Server -> Networking -> Edit Reverse DNS for IPv4/IPv6 -> Set to mail.yourdomain.com.
• DigitalOcean: Networking -> Floating IPs or Droplet Settings -> Rename Droplet to match your FQDN (DO automatically sets PTR to the Droplet name).
• AWS EC2: EC2 Console -> Elastic IPs -> Select IP -> Actions -> Modify reverse DNS -> Enter your verified domain.
• Linode (Akamai): Linodes -> Select Instance -> Network -> Edit Reverse DNS -> Enter FQDN.

6. How to Test & Debug rDNS with CLI Tools

You can instantly verify your rDNS setup using standard terminal commands:

# Linux / macOS dig reverse lookup:
dig -x 198.51.100.50 +short

# Windows nslookup reverse lookup:
nslookup 198.51.100.50

# Verify Forward Confirmation:
host mail.yourbrand.com
        

7. How CentricSell Mail Manages Your Sending IPs

With CentricSell Mail, you never have to worry about broken PTR records ruining your domain reputation:

• Automatic Server Provisioning: When you connect your own VPS, CentricSell Mail configures Postfix, tests your PTR record over SSH, and verifies FCrDNS alignment before enabling outbound traffic.
• Multi-ESP Fallback: If your dedicated IP encounters greylisting or rate limits, traffic seamlessly shifts to AWS SES or SendGrid with established high-reputation IPs.