Reverse DNS vs Forward DNS: What Is the Difference?
A practical explanation of forward DNS and reverse DNS, how A/AAAA lookups differ from PTR lookups, and why the two directions answer different questions.
Forward DNS and reverse DNS are related, but they are not mirror images in the way people often assume.
They answer different questions.
Forward DNS asks “where does this hostname point?”
This is the normal lookup people mean when they say “DNS lookup.”
Examples:
ArecordAAAArecordCNAME
The basic question is:
given a hostname, which address or alias does it resolve to?
Reverse DNS asks “what hostname points back to this IP?”
This is the PTR side.
The basic question is:
given an IP, is there a reverse hostname for it?
That is why reverse DNS is often discussed in mail and infrastructure contexts rather than in day-to-day browsing.
Why they should not be confused
A forward lookup can exist without a useful reverse lookup.
A reverse lookup can exist and still not tell you much about the real service context.
That is normal.
Forward DNS is usually more important for websites
If you are trying to understand:
- where a website points
- whether IPv4 or IPv6 is configured
- which nameserver is authoritative
then forward DNS is usually the main event.
Useful follow-ups:
Reverse DNS is often more important for infrastructure and mail
If you are trying to understand:
- a sender IP
- a mail reputation clue
- a hosting naming pattern
then reverse DNS becomes more useful.
Useful follow-ups:
The short version
Forward DNS starts with the hostname and finds the address.
Reverse DNS starts with the IP and looks for a hostname.
They complement each other, but they do not answer the same question.
Continue reading
Stay in the same investigation track with these closely related guides.
Tools mentioned in this article
Run the same diagnostics to follow along with the guide.