What Is Reverse DNS?
Reverse DNS looks up a name associated with an IP address, commonly using a PTR record. Forward DNS answers a different question by resolving a name to an address. For email, reverse DNS is part of identifying the infrastructure that actually connects to a receiving server.
By LeadHaste Editorial · AI-assisted editorial review ·
Start with the actual sending address
A business's website address may have nothing to do with the IP used to send its email. Obtain the sending source from the relevant message or provider log before checking reverse DNS. A clean lookup for the wrong address does not help explain a rejection involving a different mail server.
In a conceptual example, a sending provider operates the IP while the customer controls example.com. The provider may also control the reverse-DNS configuration. Record that ownership boundary before opening an incident with the person who manages the customer's ordinary DNS zone; that person may have no authority to change the relevant PTR record.
Forward and reverse observations belong together
Some receiver requirements involve a meaningful reverse name and a corresponding forward lookup. Google's sender guidance includes valid forward and reverse DNS for sending IP addresses. Confirm the exact provider's current requirement and inspect both directions rather than treating any nonempty PTR answer as a complete configuration test.
A matching name does not authenticate the visible From address, establish recipient permission or guarantee inbox placement. SPF, DKIM, DMARC and filtering answer other questions. Preserve the full rejection text so a reverse-DNS finding can be connected to the condition the receiving system actually reported for that message.
How to assign the repair
Identify who operates or allocates the IP address and which supported process they use for reverse DNS. For shared sending infrastructure, the appropriate action may be a provider support case rather than a customer DNS edit. Avoid copying an unrelated hostname simply to make a public checker display a result.
After an authorized change, read back the reverse answer, inspect the corresponding forward resolution and test the affected mail path. Record the address, hostname, provider response and observation time. This establishes which infrastructure was checked and prevents a later operator from confusing a corrected DNS relationship with proof that every delivery issue has been resolved.
Sources
Useful next steps
Related terms
Put the pieces into a system you own.
Explore your ICP and campaign fit on a free discovery call, then decide what your outbound operation needs.
Book your free ICP review →