Keep one item on each line
Blank lines are ignored, but physical line numbers, duplicates and order are preserved. Mix IPv4 reverse DNS and IPv6 reverse DNS inputs in one batch; do not paste a URL, a hostname or a port.
DNS & Domains
Enter one IP address or CIDR per line. Addresses produce PTR owner names; aligned prefixes produce zone names.
Addresses are processed in this browser. No DNS request is sent.
An undotted name can be relative to a zone-file origin.
IPv6 expands to 32 hex digits. Each digit becomes a reversed label; IPv4 reverses whole octets.
Maximum 100 nonempty lines and 65,536 UTF-16 units. JSON keeps failed rows; names export requires every row to succeed.
Open DNS lookupWaiting to generate the latest input…
Use a reverse DNS generator when a change request needs the exact owner name beneath in-addr.arpa or ip6.arpa. Reversing the written groups of a compressed IPv6 address is not enough: omitted zeros must be restored, then every hexadecimal digit reversed. Compare the expanded address with the name before adding it to a DNS configuration.
The reverse DNS generator treats an IPv4 octet as one label, while IPv6 uses one hexadecimal digit per label. The input stays intact and the expanded form remains beside each result, so an abbreviated address can be reviewed without mental zero counting.
A host produces its complete PTR owner. A CIDR produces one zone for its network prefix, with host bits cleared only in the displayed network. The result marks the two cases separately; a /24 never turns into a list of 256 host records.
Blank lines are ignored, but physical line numbers, duplicates and order are preserved. Mix IPv4 reverse DNS and IPv6 reverse DNS inputs in one batch; do not paste a URL, a hostname or a port.
For 192.0.2.129/24, the network is 192.0.2.0/24 and the zone is 2.0.192.in-addr.arpa. The original host bits are not turned into extra labels. Nonaligned prefixes are rejected rather than enlarged.
Names export is blocked when any row fails. Select JSON to retain the entire report, including errors. Turn automatic generation off for the Generate button or Ctrl/Cmd + Enter; changing an option makes the previous result stale immediately.
IPv4 requires four decimal octets from 0 to 255. IPv6 accepts full or compressed notation, including a dotted IPv4 tail. An IPv4-mapped IPv6 address remains IPv6 and produces an ip6.arpa name, not an in-addr.arpa alias.
IPv4 prefixes must be multiples of eight and IPv6 prefixes multiples of four. The /0 result is the reverse tree root. A /32 IPv4 or /128 IPv6 input covers one address and is marked as a host.
Each JSON row contains the original text, source line, address family, kind, expanded address, network, generated name and stable error codes. The first 50 rows appear initially; Show more reveals the remaining rows. Exports include the whole batch.
Reverse the four decimal octets, keep each octet intact and append in-addr.arpa. For 192.0.2.1 the absolute owner is 1.2.0.192.in-addr.arpa. This is the record name; it does not supply the hostname stored in the PTR record.
An IPv6 address has 128 bits. Each hexadecimal digit represents four bits, so the full address has 32 digits. Expand compressed zeros first, reverse those digits individually and append ip6.arpa; reversing only the eight colon-separated groups would be wrong.
This page accepts IPv4 prefixes /0, /8, /16, /24 and /32, plus IPv6 prefixes divisible by four through /128. It masks host bits for a CIDR. Other prefix lengths can require multiple zones or classless delegation, which this tool deliberately does not generate.
RFC 2317 describes classless IPv4 reverse delegation using coordination between parent and child zones, including CNAME records. The necessary names and delegation agreement cannot be inferred from a prefix alone, so this page reports an unsupported boundary instead of inventing that configuration.
Only if you control the reverse zone or your address provider gives you a reverse-DNS setting or delegation. Controlling a normal domain does not automatically give control of the IP block. Take the generated owner name to the provider responsible for that address.
No. It computes an owner or zone name from the entered address. A successful result can still have no live PTR record. An actual lookup is a separate operation and is not triggered by editing, generating, copying or downloading here.
Have a prefix or address case to check?
Return to the reverse DNS generator, check the host or zone marker, and export a complete list or a report with the rejected lines.