IP Address Today

Reverse DNS name generator

Give it an address and it returns the PTR name to query. Give it a block and it returns the reverse zones you would need delegated — or explains why a block smaller than a /24 cannot be delegated as a zone at all.

Try:
in-addr.arpa name
1.2.0.192.in-addr.arpa
Query it(dig does the reversing for you)
dig -x 192.0.2.1 +short

What a reverse lookup actually does

There is no special protocol for "which name owns this address". Reverse DNS is an ordinary lookup of an ordinary name in an ordinary tree — the trick is entirely in how the name is constructed. 192.0.2.1 becomes 1.2.0.192.in-addr.arpa, and a PTR record there holds the hostname.

Because it is just DNS, the same delegation rules apply: whoever is delegated the zone controls the answers, and nothing forces those answers to agree with the forward tree.

Where zones can be split

Reverse DNS delegation boundaries
Block sizeReverse zonesDelegable?
/81 zone (e.g. 10.in-addr.arpa)Yes
/161 zoneYes
/241 zoneYes
/224 × /24 zonesYes, as four delegations
/25 to /32Part of one /24 zoneNo — RFC 2317 CNAMEs instead
IPv6 /481 zone under ip6.arpaYes, on a nibble boundary

Frequently asked

Why are the octets reversed?
DNS delegates from the right: com is delegated, then example.com beneath it. An IPv4 address is written the other way round, most-significant octet first. Reversing it lines the two up, so that 10.in-addr.arpa can be delegated as a single subtree covering everything in 10.0.0.0/8.
Why does IPv6 use one label per nibble?
So that delegation can happen on any four-bit boundary, which matters because IPv6 allocations are made on nibble boundaries. It makes the names long — a single address is 32 labels plus ip6.arpa — but it means a /48 or a /56 can be delegated cleanly, which an octet-based scheme could not manage.
Can I get reverse DNS for a /26?
Not as a delegated zone, because a zone cannot be smaller than a /24 in the in-addr.arpa tree. RFC 2317 is the standard workaround: the /24 holder keeps the zone and adds CNAME records pointing each address into a zone you do control. Most ISPs offer this, or simply set PTR records for you on request.
Does a PTR record prove anything about the host?
Only that whoever controls the address block said so — the forward and reverse trees are administered separately. That is why forward-confirmed reverse DNS exists: resolve the PTR to a name, then resolve that name back to an address, and check it matches. Mail servers do this routinely; a PTR alone is not evidence.

Doing this for thousands of addresses?

These calculators run in your browser and never send us your input. When you need geolocation, ASN and network data for addresses in bulk, the API answers in one call — no key required to try it.

curl https://api.ipaddresstoday.com/api/v1/8.8.8.8

Other free tools