Reverse DNS and PTR Records Explained
Normal, or forward, DNS starts with a name and returns an address. Reverse DNS starts with an IP address and asks whether the address owner published a hostname. The result is stored in a PTR record.
How reverse lookup names are constructed
For IPv4, the octets are reversed and placed under in-addr.arpa. The address 8.8.8.8 becomes 8.8.8.8.in-addr.arpa. IPv6 uses reversed hexadecimal nibbles under ip6.arpa.
Who controls the PTR record?
The organization controlling the IP range normally controls reverse DNS. That is often a hosting provider, internet provider, cloud platform, or corporate network operator. Owning a domain name does not automatically let you set reverse DNS for an unrelated address.
Why email servers care
Mail systems often compare forward and reverse DNS as one signal when assessing a sending server. A consistent hostname can support good operational hygiene, but it does not replace SPF, DKIM, DMARC, reputation, rate control, or secure server configuration.
Why no hostname may appear
- The IP owner never created a PTR record.
- The record was removed or is still propagating.
- The address is dynamically assigned to customers.
- The public resolver cannot reach authoritative reverse-DNS servers.
- The address belongs to a private or documentation-only range.
What a PTR result proves
A PTR record shows the hostname the address owner chose to publish. It does not prove that a website is safe, that a person owns the address, or that the name is current. Attackers can control DNS for systems they own, so reverse DNS should never be the only trust decision.