What reverse DNS does
Ordinary, or forward, DNS helps a client find an IP address for a name. For example, an A record can associate a hostname with an IPv4 address, while an AAAA record can associate it with an IPv6 address. Reverse DNS starts at the other end: given an IP address, it looks for a name in a PTR record. PTR stands for “pointer.”
A reverse lookup is useful when a person or system wants a recognizable name for an address found in a connection log. It can also be one part of how a receiving mail server evaluates a sending server. A PTR result is not proof of who operates a machine, however. It is a DNS answer that must be interpreted alongside other information.
The two directions are separate. Adding an A record for a hostname does not automatically create a PTR record for its address, and changing a PTR record does not update forward DNS. A hostname can resolve to several addresses, while an address has its own reverse DNS entry or entries. When consistency matters, check both directions rather than assuming they agree.
How an address becomes a reverse lookup name
Reverse DNS uses special DNS namespaces. For IPv4, the namespace is in-addr.arpa. To look up the illustrative address 192.0.2.10, a resolver reverses its four number groups and queries for a PTR record at 10.2.0.192.in-addr.arpa. That record might point to a name such as server.example.com. The reversed order follows the way DNS names are delegated, allowing authority over an address range to be assigned within the reverse namespace.
IPv6 uses ip6.arpa. Its reverse lookup names are built by reversing the individual hexadecimal digits of the full IPv6 address, rather than reversing groups of numbers as with IPv4. The resulting name is long, but the underlying idea is the same: query the reverse DNS namespace for a PTR record and read the name it returns.
The name in a PTR record is a DNS hostname, not a web address. A reverse lookup does not tell you whether a website exists there, which service is listening, or whether a browser can connect. Those questions require separate checks.
Who can set a PTR record?
The party that controls reverse DNS for an IP address is often the network or hosting provider that assigned it. If you rent a server, you may need to set its PTR name in your provider’s control panel or ask the provider to do it. Managing the DNS zone for your domain alone does not necessarily give you control over reverse DNS for the server’s address.
There are exceptions: an organization with its own address space may manage its reverse DNS directly or arrange a delegation from its provider. The practical first step is to identify who supplies the IP address and check how that provider handles reverse DNS. Before requesting a change, decide which stable hostname should represent the address and ensure that its forward A or AAAA record is configured as intended.
A provider may impose rules on allowed PTR names or on how many names can be assigned. If an address is shared by several services, its PTR name cannot be expected to describe every domain hosted there. Choose a name that fits the role of the address rather than treating a PTR record as a directory of all its websites.
Checking results and understanding mismatches
A DNS lookup tool can query an address’s PTR record. A practical check has two steps: look up the IP address in reverse DNS, then look up the returned hostname in forward DNS. If the forward result includes the original IP address, the two directions are consistent for that pair. Some software uses this kind of forward-confirmed reverse DNS check, but a matching pair alone does not establish identity or trust.
If a lookup returns no PTR record, confirm that you entered the intended public IP address and are checking the address your service actually uses. If the returned name is unexpected, check whether the address belongs to a hosting provider, is shared, or recently changed hands. DNS answers can also remain cached for a time after a change, so compare results again after the relevant cache lifetime has passed.
When troubleshooting, keep the checks distinct: a failed reverse lookup is different from a hostname that has a PTR record but no matching forward address. Recording the queried IP, the returned PTR name, and the forward lookup result makes it easier to explain a problem to the provider that controls the address.
Where PTR records fit in a DNS setup
Reverse DNS is especially worth checking for a server that sends email directly. Receiving systems may consider whether the sending IP has a sensible PTR name and whether that name resolves back to the IP. Their policies vary, and a well-configured PTR record does not guarantee delivery. SPF, DKIM, and DMARC serve different purposes and should not be treated as substitutes for, or consequences of, reverse DNS.
For a typical website visitor, forward DNS is what gets the browser to the server. PTR records are most helpful for identifying addresses during diagnostics and for services that explicitly consult reverse DNS. The key distinction is simple: domain owners usually manage names pointing to addresses, while reverse DNS for an address is managed through whoever controls that address’s reverse namespace.
