Networking Fundamentals
What Is a Reverse DNS (PTR) Lookup?
Normal DNS turns a name into an IP address. Reverse DNS does the opposite — it turns an IP address back into a name.
DNS in reverse
A regular ("forward") DNS lookup answers, "What IP address does example.com use?" A reverse DNS lookup answers the opposite: "What hostname is associated with this IP address?" The result is often something like host-203-0-113-5.example-isp.net — the name your ISP publishes for your address.
How it works: PTR records
Reverse lookups use a special record type called a PTR (pointer) record. To make reverse lookups fit into the normal DNS hierarchy, the IP address is reversed and placed under a special domain. An IPv4 address like 203.0.113.5 is queried as 5.113.0.203.in-addr.arpa; IPv6 uses a similar scheme under ip6.arpa. The owner of the address block controls these records.
Why reverse DNS matters
- Email reputation: mail servers often reject or distrust senders whose IP address has no matching reverse DNS record. Proper reverse DNS is considered a sign of a legitimately run server.
- Diagnostics and logs: a hostname is far more meaningful than a bare number when reading server logs or tracing a network path.
- Identifying the network: the hostname often hints at the ISP and region, since providers embed those in the naming scheme.
Forward and reverse can disagree
There is no rule that a name and address must match in both directions, and often they don't. An IP's reverse record might point at a name that doesn't resolve back to the same address. Mail systems sometimes check for agreement ("forward-confirmed reverse DNS") as an extra trust signal.
See it yourself
IP Ducky performs a reverse DNS lookup on your address and shows the hostname your ISP has published for it, along with the record's time-to-live. It is a small window into how your connection is labeled by the network that provides it.