What reverse DNS tells a receiving server
When a mail server connects to another server to deliver a message, the receiving server can see the connecting IP address. Reverse DNS lets it look up a hostname for that IP address. This lookup uses a PTR record, which maps an address to a name—the opposite direction from the A or AAAA records used to look up an address from a hostname.
For example, an outgoing server at the documentation address 192.0.2.25 might have a PTR record that returns mail.example.net. That gives the receiver a name to associate with the connecting server. It does not prove who wrote the message or whether the message is wanted. A PTR record is one signal a receiver can consider when assessing a connection.
The organization that controls the IP address or its reverse-DNS zone usually controls the PTR record. If you rent a server, this may mean setting the record in your hosting provider’s control panel or requesting a change from the provider. Adding a PTR record to the ordinary DNS zone for your domain will not, by itself, configure reverse DNS for the server’s IP.
How forward-confirmed reverse DNS works
Forward-confirmed reverse DNS, often shortened to FCrDNS, checks the relationship in both directions. First, the receiver looks up the connecting IP’s PTR record and gets a hostname. Then it looks up that hostname’s address records. If one of the returned addresses matches the connecting IP, the hostname is forward-confirmed.
In the example above, the PTR for 192.0.2.25 returns mail.example.net. An A lookup for mail.example.net would need to include 192.0.2.25 for the IPv4 connection to pass that check. A hostname can have more than one address; the relevant test is whether the connecting address appears among them. For a server connecting over IPv6, check the IPv6 address’s PTR and the hostname’s AAAA records separately.
A successful check shows that the reverse name and forward address records agree. It is not a guarantee of delivery or a replacement for email authentication. Receiving systems vary in how they use the result, but missing or inconsistent records can make an outgoing server look poorly configured.
Choose a stable hostname for the sending server
A practical setup starts with a hostname intended for the outgoing server, such as mail.example.net. Create an A record, or an AAAA record if the server sends over IPv6, pointing that name to the address it actually uses for outbound connections. Then ask the IP provider to set that address’s PTR record to the same hostname.
Check the hostname the server presents in its SMTP EHLO or HELO greeting as well. Using the same stable, resolvable hostname there can make the server’s identity easier to understand and troubleshoot. EHLO and the PTR record are separate settings, however, so changing one does not automatically change the other.
If an application sends through a hosted relay, the relay’s public IP—not the application server’s IP—is what the recipient normally sees for that SMTP connection. In that case, the relay provider generally manages the relevant PTR records. If you operate several outgoing IP addresses, review the PTR and forward records for each address that may connect to recipients.
Keep reverse DNS distinct from email authentication
Reverse DNS identifies a hostname associated with the connecting IP. It does not need to match the visible From address in every message. SPF, DKIM and DMARC address different questions about whether a domain authorizes or takes responsibility for a message. A server can have correct forward-confirmed reverse DNS while its domain authentication is misconfigured, or the reverse can be true.
For reliable sending, treat these as complementary checks. Confirm that the sending service is using the expected outbound IPs, that the relevant domain’s authentication records reflect the service you use, and that the server’s PTR and forward records agree. No single DNS record guarantees inbox placement: recipients can also consider message content, sending behavior and their own policies.
Check the records when delivery fails
Start with the public IP address that actually connects to the recipient. A reverse lookup, such as dig -x 192.0.2.25, shows its PTR result. Then look up that result with a command such as dig A mail.example.net and confirm that the answer includes the original IPv4 address. For an IPv6 connection, reverse-lookup its IPv6 address and check the returned hostname’s AAAA records instead.
If the PTR is absent or wrong, contact whoever manages the IP address. If the forward lookup is wrong, update the hostname’s A or AAAA record with the DNS provider for that domain. After a change, cached answers may remain visible for a while, so check again after caches have had time to refresh. If both directions agree but mail is still rejected, read the receiving server’s response and investigate other possible causes rather than assuming reverse DNS is the problem.



