Forward DNS looks up an address from a name; reverse DNS looks up a name from an address, usually with a PTR record. The organization controlling the address block normally controls reverse DNS. A PTR name is a label, not proof of a person’s identity or a service’s safety.
How the reverse lookup is organized
IPv4 reverse lookup names use reversed octets under in-addr.arpa. For the documentation address 192.0.2.25, the query name is 25.2.0.192.in-addr.arpa. IPv6 reverse names use individual hexadecimal digits in reverse order under ip6.arpa. Tools normally build these names for you.
A forward A or AAAA record and a reverse PTR record live in different DNS zones. Creating server.example.com in your domain does not automatically grant you control over the reverse record of its public IP.
Query a PTR without guessing a hostname
# Replace the documentation address with the IP you are investigating
nslookup -type=PTR 25.2.0.192.in-addr.arpa
# With dig installed
dig -x 192.0.2.25A missing answer can mean that no PTR exists, the resolver could not complete the lookup, or the reverse zone is misconfigured. Inspect the reported response rather than treating all failures as the same. A default ISP hostname can be completely normal for a residential address.
Set reverse DNS at the address provider
For a VPS, look for reverse-DNS settings in the hosting control panel or contact the host. For a business connection, ask the ISP. Choose a hostname that you control and publish its forward address record as appropriate. Some providers verify that the forward name already points back to the address before accepting the PTR change.
When running a mail server, forward-confirmed reverse DNS is often part of the recipient's checks: the PTR gives a name and the forward lookup should include the sending IP. It is one operational requirement, not a guarantee that mail will be accepted or avoid spam filtering.
Read reverse names with restraint
A traceroute may display a router name containing a city code, link speed, or operator abbreviation. Those labels can be helpful clues, but may be outdated or refer to an administrative location rather than the exact physical route. Confirm conclusions with measured behavior and operator information.
PTR records can change, addresses can be reassigned, and several devices may share an IPv4 address behind NAT. Do not use a reverse name as authentication. TLS certificates, account credentials, and service-specific authorization address different trust questions.
For troubleshooting, save the original address alongside the displayed name and timestamp. If a tool spends a long time resolving hop names, repeat its test with numeric output so DNS delay does not get confused with the underlying route latency.
Put it into practice
References & further reading
Protocol standards and official documentation supporting this guide. Device menus and provider policies vary; use the documentation for your equipment when applying a change.