Topic · Email Infrastructure

Reverse DNS

Reverse DNS maps an IP address back to a hostname using a PTR record. The reverse zone is generally controlled by the address owner.

Email Security Glossary·Practical guidance
Share this definition LinkedIn X WhatsApp Email
01 / How it works

How it works

Receivers often compare PTR and forward DNS consistency when evaluating sending infrastructure.

02 / What can go wrong

What can go wrong

Missing or generic reverse DNS can harm sender reputation despite valid DMARC.

03 / What to check or do

What to check or do

Coordinate PTR, A or AAAA and EHLO hostname assignments with the IP owner.

Practical scenario

Practical scenario

A dedicated sending IP authenticates with SPF and DKIM, but its PTR record is missing or refers to a generic cloud hostname inconsistent with its forward mapping. Some receivers use identity and DNS hygiene signals in addition to authentication.

Verification checklist

  1. Query PTR for the exact sender IP and resolve its hostname forward.
  2. Ensure the hostname and corresponding address mapping are coherent.
  3. Check that the server greeting and provider configuration are appropriate.
  4. Request rDNS changes from the IP owner when the customer cannot edit them directly.
Practical diagnosis

How to investigate Reverse DNS

Signal to investigate
A dedicated IP lacks a PTR hostname while the SMTP banner uses a branded name.
Evidence to collect
Query reverse PTR and forward A/AAAA for the hostname, then compare sender configuration.
Common wrong conclusion
Reverse DNS is normally controlled by the IP owner, not by editing the domain's ordinary zone.

How to interpret the evidence

Reverse DNS maps an IP address back to a hostname via PTR, and many operators also check whether that hostname resolves forward to the sender IP. The PTR record typically belongs to the IP network owner. An email authentication domain's DNS zone cannot necessarily change the PTR of a cloud or ESP-owned address.

What to change and how to verify it

Ask the network or ESP owner to configure the intended PTR, verify reverse and forward resolution, then compare the EHLO identity and provider recommendations. Treat rDNS as infrastructure hygiene—not as proof of DKIM, SPF or DMARC alignment.

Illustrative diagnostic — substitute your authorized domain or host
dig +short -x 192.0.2.10
Educational example; not validated against your live infrastructure.
NEXT STEP

Put this into practice

Run a focused check, then explore protection if your domain needs it.