Reverse DNS (PTR Records): Why They Matter for Email Deliverability (2026)

What Is Reverse DNS?

Standard DNS (forward DNS) maps a hostname to an IP address. Reverse DNS does the opposite: it maps an IP address back to a hostname. This is accomplished through PTR (Pointer) records stored in a special DNS zone.

For IPv4, reverse DNS uses the in-addr.arpa domain. The IP address octets are reversed and appended to this domain. For example, the PTR record for IP 203.0.113.25 would be queried at:

25.113.0.203.in-addr.arpa.  IN  PTR  mail.example.com.

For IPv6, reverse DNS uses the ip6.arpa domain with each nibble (half-byte) of the expanded address reversed. For example, the address 2001:db8::1 becomes a very long query name with each hex digit separated by dots.

How PTR Records Work

Unlike regular DNS records (A, MX, TXT) which are managed by the domain owner, PTR records are managed by the IP address block owner. This is typically your hosting provider, ISP, or cloud provider (AWS, Azure, Google Cloud, DigitalOcean, etc.).

The reverse DNS zone is delegated through the Regional Internet Registries (RIRs) like ARIN, RIPE, and APNIC to whoever owns the IP block. When you lease a server or IP address, you typically need to request PTR record setup through your provider's control panel or support team.

Key characteristics of PTR records:

• One PTR per IP. Best practice is to have exactly one PTR record per IP address. Multiple PTR records are technically valid but can cause issues with some mail servers.
• Hostname must resolve. The hostname in the PTR record should have a corresponding A or AAAA record that resolves back to the same IP address.
• Managed by IP owner. You cannot set PTR records in your domain's DNS zone. They must be configured by whoever controls the IP address block.

What Is FCrDNS (Forward-Confirmed Reverse DNS)?

FCrDNS is a validation technique that verifies the consistency between forward and reverse DNS. It works in two steps:

1. Reverse lookup: Start with the IP address and look up its PTR record to get a hostname.
2. Forward lookup: Take that hostname and look up its A or AAAA record. If the resulting IP matches the original IP, the address has valid FCrDNS.

# Step 1: Reverse lookup
203.0.113.25 → PTR → mail.example.com

# Step 2: Forward lookup
mail.example.com → A → 203.0.113.25

# Result: FCrDNS passes (IP matches)

FCrDNS is important because it proves that the IP address owner and the domain owner have a relationship. An attacker who controls an IP but not the domain cannot create a valid FCrDNS mapping. Many mail servers and spam filters check for FCrDNS as a basic trust indicator.

Why Mail Servers Check PTR Records

Virtually all major mail servers and spam filters verify reverse DNS as part of their incoming mail evaluation. Here is why PTR records are critical for email:

• Spam filtering signal. Legitimate mail servers almost always have PTR records. Spammers operating from compromised machines or rented botnet IPs typically do not. Missing rDNS is a strong spam indicator.
• Gmail requirements. Google explicitly requires sending IPs to have valid PTR records. Emails from IPs without rDNS are more likely to be marked as spam or rejected outright.
• Microsoft 365 checks. Exchange Online Protection performs rDNS verification and uses it as a factor in its spam confidence level (SCL) scoring.
• RFC compliance. RFC 1912 recommends that every internet-reachable host should have a PTR record. RFC 7208 (SPF) also references rDNS in its verification mechanisms.
• IP reputation. PTR records associate an IP with an identity. IPs without rDNS have no identity and are treated with suspicion by reputation systems.

Common rDNS Problems and Their Impact

• No PTR record at all. Many mail servers will reject or spam-flag emails from IPs without any reverse DNS. This is the single most common rDNS issue.
• Generic ISP hostname. PTR records like pool-203-0-113-25.isp.com indicate a residential or dynamically assigned IP. Mail servers heavily penalize these because legitimate mail servers use static IPs with meaningful hostnames.
• FCrDNS failure. If the PTR hostname does not resolve back to the same IP, the FCrDNS check fails. This is worse than having no PTR record because it suggests misconfiguration or suspicious activity.
• Mismatched HELO/EHLO. When your mail server connects to another server, it announces its hostname via the SMTP HELO/EHLO command. Ideally, this hostname should match the PTR record. Mismatches can trigger additional spam scoring.

How to Set Up PTR Records

Setting up reverse DNS depends on your hosting provider. Here are instructions for common providers:

Cloud Providers (AWS, Azure, GCP)

• AWS: Submit a reverse DNS request through the EC2 console or AWS Support. You need an Elastic IP with a PTR record request.
• Azure: Configure the PTR record in the Azure portal under the Public IP address resource's DNS name label.
• Google Cloud: Set the PTR record through the Compute Engine instance's network interface configuration.

VPS Providers (DigitalOcean, Linode, Vultr)

Most VPS providers offer PTR record configuration directly in their control panel. Look for a "Reverse DNS" or "PTR Record" option in your droplet/instance networking settings. Some providers automatically set the PTR to match the hostname you assign to the server.

Dedicated Hosting / Colocation

Contact your provider's support or network operations team to request PTR record configuration. If you own your own IP block and have it registered with an RIR, you can manage reverse DNS zones yourself.

Best Practices for Email rDNS

• Use a meaningful hostname. Set the PTR to something like mail.example.com rather than a generic name. The hostname should clearly identify it as a mail server for your domain.
• Ensure FCrDNS passes. The PTR hostname must have an A record that resolves back to the same IP. Test with our Reverse DNS tool.
• Match SMTP HELO. Configure your mail server's HELO/EHLO hostname to match the PTR record.
• Include in SPF. Ensure the IP address is included in your SPF record, either directly or via an include mechanism.
• Check blacklists. Even with proper rDNS, your IP may be on a blacklist. Regularly monitor your IP reputation.

How to Check Your Reverse DNS

Use our free tools to verify your rDNS configuration:

• Reverse DNS Lookup — Look up the PTR record for any IP address and verify FCrDNS.
• Email Verifier — Check overall email deliverability including rDNS verification.
• Blacklist Checker — Ensure your sending IP is not listed on any major blacklists.