PTR records and reverse DNS for mail servers: why FCrDNS matters
AdminKit explains why a PTR record matters for mail delivery: it resolves an IP back to a hostname, the reverse of an A/AAAA lookup, and receiving mail servers often check that a sending IP has one that also resolves forward to the same address — forward-confirmed reverse DNS — so a missing or mismatched PTR commonly gets mail rejected.
By AdminKit team, Netbase JSC · Updated
Key takeaways
- A PTR record maps an IP address back to a hostname. It lives in a zone run by whoever holds the IP block (your hosting provider or ISP), not in your domain’s DNS.
- Receivers check more than “a PTR exists”: forward-confirmed reverse DNS means the PTR name must resolve back to the same sending IP.
- Gmail’s sender guidelines require valid forward and reverse DNS for every sender, and its IPv6 rules mean each IPv6 sending address needs its own PTR.
- Fix it by setting the forward A/AAAA record first, then asking the IP’s owner to set the PTR to that name, and use the same name in your server’s EHLO greeting.
What does reverse DNS actually resolve?
A normal DNS lookup takes a hostname and returns an IP address. Reverse DNS does the opposite: it takes an IP address and returns a hostname, using a dedicated DNS record type (PTR) stored in a special zone — in-addr.arpa for IPv4, defined in RFC 1035 (also on the IETF Datatracker), or ip6.arpa for IPv6, added by RFC 3596. The lookup is structured as the IP’s octets or nibbles in reverse order under that zone, which is why it needs its own record type rather than reusing an ordinary A or AAAA record. AdminKit’s reverse DNS (PTR) tool performs this lookup for any IPv4 or IPv6 address and shows the hostname it resolves to, if any.
Here is the name a resolver actually queries for one IPv4 and one IPv6 sending address (documentation addresses):
192.0.2.25 -> 25.2.0.192.in-addr.arpa. PTR mail.example.com.
2001:db8::25 -> 5.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa. PTR mail.example.com.
IPv4 reverses the four octets. IPv6 expands the address to all 32 hex digits and reverses them one nibble at a time, which is why IPv6 reverse names are long. AdminKit’s PTR record generator computes these names in your browser if you want to check a value before asking for it.
Who controls the PTR record?
A PTR record is not controlled by the operator of a website or mail domain — it’s controlled by whoever owns the IP address block the address comes from, which for most senders means a hosting provider, cloud platform, or ISP. This is the single most important fact to understand before troubleshooting a PTR problem: you usually cannot fix a missing or wrong PTR record yourself by editing your own domain’s DNS, because it lives in a zone your DNS provider doesn’t control.
There is one case where you may end up running part of the reverse zone yourself. If a provider assigns you a block smaller than a /24, the reverse zone boundary doesn’t line up with your addresses. RFC 2317 describes the standard workaround: the provider publishes CNAME records in its zone that point each of your addresses into a small sub-zone it delegates to you (illustrative, for a /25):
; in the provider's 2.0.192.in-addr.arpa zone
0/25 IN NS ns1.example.com.
25 IN CNAME 25.0/25.2.0.192.in-addr.arpa.
; in your 0/25.2.0.192.in-addr.arpa zone
25 IN PTR mail.example.com.
If your provider tells you reverse DNS for your range is “delegated to you”, this is usually what they mean, and the PTR goes into that sub-zone on your own name servers.
Why do mail servers specifically care?
Reverse DNS predates modern mail authentication (SPF, DKIM, DMARC) by decades, and it survives as a check because it’s cheap, requires no cooperation from the sender’s domain, and catches a specific category of low-effort abuse: mail sent directly from a compromised consumer device, a botnet node, or a throwaway cloud instance that was never configured as a real mail server. Legitimate mail infrastructure is set up deliberately — someone requested a PTR record, which means someone took a configuration step that abuse infrastructure usually skips. A missing PTR record doesn’t prove malicious intent, but its absence correlates strongly enough with abuse sources that many receiving mail servers treat it as a meaningful signal, sometimes enough on its own to reject a connection outright.
This has moved from best practice into published requirements. Google’s email sender guidelines list, for every sender to Gmail regardless of volume, “Ensure that sending domains or IPs have valid forward and reverse DNS records, also referred to as PTR records”, and spell out what valid means: the sending IP must have a PTR record that resolves to a hostname, and that hostname must have an A or AAAA record resolving to the same IP.
How does forward-confirmed reverse DNS work?
Checking the PTR record alone has a gap: nothing stops whoever controls an IP block from publishing any hostname they like in the PTR record, including one that implies legitimacy it doesn’t have. Forward-confirmed reverse DNS closes that gap by checking both directions: look up the PTR record for the sending IP to get a hostname, then look up that hostname’s own A or AAAA record and confirm it resolves back to the same IP. If both directions agree, the sending IP and the claimed hostname are mutually consistent — not cryptographically proven, since DNS itself isn’t signed by default, but a meaningfully stronger signal than a PTR record checked in isolation. Many receiving mail servers perform exactly this two-step check before accepting a connection, which is why a correctly configured mail server needs both a PTR record pointing at a hostname, and that hostname’s forward record pointing back at the same IP. Industry sender guidance treats this as baseline hygiene: the M3AAWG Senders Best Common Practices cover reverse DNS among the signals a legitimate sending host should get right.
The manual version of the check is two commands (illustrative output; documentation addresses):
$ dig -x 192.0.2.25 +short
mail.example.com.
$ dig A mail.example.com +short
192.0.2.25
Both answers agree, so FCrDNS passes. RFC 1912, a long-standing list of common DNS errors, adds two details that trip people up: the PTR must point to a name with a real A record, not to an alias defined by a CNAME, and a host with several addresses needs a matching PTR for every address it uses, not just the first.
Does the EHLO name have to match the PTR?
Not by the letter of the SMTP standard, but in practice you should make them match. RFC 5321 §4.1.4 says the sending server must, if possible, give its primary host name in the HELO/EHLO greeting. A receiver may check that this name corresponds to the client’s IP address, but the RFC says it must not refuse a message on that basis alone. Receivers’ own policies go further than that minimum, and a server that announces mail.example.com, has a PTR of mail.example.com and an A record pointing back gives every check the same answer.
Which misconfigurations break reverse DNS for mail?
Most problems fall into a handful of patterns. Each one is visible with the two dig commands above:
| What you see | Cause | Fix |
|---|---|---|
| No PTR at all | New cloud instances and VPS often start without one | Ask the IP’s owner to set one, after creating the forward record |
| PTR is a generic provider name (for example built from the IP digits) | The provider’s default was never changed | Request a PTR with your mail host’s name |
| PTR name has no A/AAAA record, or it points elsewhere | Forward record missing, changed or deleted | Create or correct the forward record so FCrDNS passes |
| PTR points to a CNAME | Alias used instead of the real host name | Point the PTR at a name with its own A/AAAA record |
| IPv4 passes, IPv6 fails | The server also sends over IPv6, which has no PTR | Add an IPv6 PTR, or bind outbound mail to IPv4 |
| EHLO name differs from the PTR | MTA hostname set to a default or internal name | Set the MTA’s hostname to the PTR name |
The IPv6 row is worth a separate check. Google’s guidelines include an example rejection, 550-5.7.1: Message does not meet IPv6 sending guidelines regarding PTR records and authentication, and say such an IPv6 authorization error can mean the PTR record for the sending server isn’t using IPv6. A dual-stack mail server can switch to IPv6 for delivery without anyone changing its configuration, so look up the PTR for the IPv6 address your server actually sends from, not only the IPv4 one.
How do you check and fix it?
- Look up your sending IP’s PTR record with AdminKit’s reverse DNS tool. No result at all means you need to request one from whoever controls the IP — see how to read a reverse DNS (PTR) lookup result if you’re unsure what the result itself is telling you.
- Check that the hostname it returns resolves forward back to the same IP, using AdminKit’s DNS lookup tool against that hostname’s A or AAAA record — this is the FCrDNS check performed manually.
- Request a specific PTR value from your hosting provider if none exists or it’s wrong; most cloud and hosting providers expose this in their control panel, and generally require the matching forward record to exist first.
- Keep the PTR hostname consistent with your mail server’s HELO/EHLO identity, since some receivers check that too.
- Repeat steps 1–2 for every address the server sends from, including IPv6.
- Treat this as one signal among several, not a complete fix for deliverability — see why is my IP address blacklisted? for the fuller picture of how sending reputation is built and damaged, and check your MX records to confirm mail is actually routing where you expect in the first place.
This guide is general information, not a security audit of your specific network — see our disclaimer for what AdminKit's guidance does and does not commit to.
Frequently asked questions
What is a PTR record, exactly?
It's a DNS record that maps an IP address to a hostname, stored in the special in-addr.arpa zone for IPv4 or ip6.arpa for IPv6 (RFC 1035, RFC 3596). It's the reverse of an ordinary lookup, which maps a hostname to an IP — hence 'reverse DNS'. Unlike a domain's own records, a PTR record is controlled by whoever owns the IP address block, not by the domain owner.
What is forward-confirmed reverse DNS (FCrDNS), and why do mail servers check it?
FCrDNS means the PTR lookup for a sending IP returns a hostname, and that hostname's own A or AAAA record resolves forward back to the same IP. Checking both directions matters because a PTR record alone can be set to anything by whoever controls the IP block; confirming the forward record agrees is a cheap way to catch a PTR that was set carelessly or doesn't correspond to a real, controlled mail host, without requiring any cryptographic signature.
My mail server's IP has no PTR record — will my email bounce?
It depends on the receiver, but a growing number of major mail providers reject or heavily penalize connections from IPs with no PTR record at all, treating it as a basic hygiene signal that a legitimate mail operator is expected to meet. A missing PTR is one of the most common, entirely self-inflicted reasons otherwise well-configured mail (correct SPF, DKIM and DMARC) still gets rejected.
Can I set the PTR record for my own server's IP?
Not directly — PTR records are published by whoever controls the IP address block, which for most senders is a hosting provider or ISP, not the domain owner. Most reputable hosting and cloud providers let you request a specific PTR value through their control panel or support, usually requiring the matching forward A/AAAA record to already exist. Residential ISPs almost never offer this, which is one reason sending mail from a home connection is unreliable regardless of how well your DNS is otherwise configured.
Does a residential IP with no PTR record mean something is wrong?
No — PTR records matter specifically for IPs that send mail. A residential or dynamic IP with a generic, ISP-assigned PTR record (or none at all) is completely normal and not a problem for ordinary browsing, gaming, or any non-mail-sending use of that connection.
Sources
- RFC 1035 — Domain Names (defines PTR records and the in-addr.arpa zone)
- RFC 3596 — DNS Extensions to Support IP Version 6 (defines ip6.arpa reverse zones)
- M3AAWG Senders Best Common Practices (reverse DNS / FCrDNS as a baseline sender hygiene signal)
- RFC 1035 — IETF Datatracker document record
- Google — Email sender guidelines (forward and reverse DNS requirement)
- RFC 1912 — Common DNS Operational and Configuration Errors (matching PTR and A records)
- RFC 5321 — Simple Mail Transfer Protocol (§4.1.4, the EHLO domain)
- RFC 2317 — Classless IN-ADDR.ARPA delegation
Want AdminKit to watch this for you?
Free checks tell you the state today. Protective DNS and monitoring tell you when it changes.
Talk to an expert
Huy Nguyen (David), Founder & CEO, Netbase JSC
Ask whether this fix applies to your setup, or get a second pair of eyes on your DNS and mail records.