Reverse DNS Lookup
Convert any IPv4 or IPv6 address into its canonical in-addr.arpa or 32-nibble ip6.arpa reverse zone name and query its PTR (Pointer) record.
Step 1 · Input IP Address
8.8.8.8
Octets (IPv4) or 32 hex nibbles (IPv6) are reversed from least-significant to most-significant boundary.
Step 2 · Derived ARPA Reverse Zone Name
8.8.8.8.in-addr.arpa
Queried with DNS record type PTR (12).
Step 3 · PTR Hostname Answer
dns.google.
TTL: 79090sCloudflare Public DNS-over-HTTPS (1.1.1.1 / application/dns-json)
How IPv4 and IPv6 Reverse DNS Zones Are Constructed
Forward DNS lookups resolve a human-readable domain name into an IP address. Reverse DNS (rDNS) performs the opposite lookup by querying a special delegated hierarchy under the .arpa top-level domain. Because DNS hierarchies read from least-specific on the right to most-specific on the left—whereas IP addresses are written with the most-significant network bits on the left—the address digits must be reversed:
- IPv4 (in-addr.arpa): The four decimal octets of 8.8.4.4 are reversed to form 4.4.8.8.in-addr.arpa.
- IPv6 (ip6.arpa, RFC 3596): The address is first expanded to all 32 hexadecimal digits (nibbles), and every single hex character is reversed and separated by dots before appending .ip6.arpa.
Why Many IP Addresses Have No PTR Record
Publishing a PTR record is optional for most client endpoints. While outbound SMTP mail servers, public DNS resolvers, and core ISP router interfaces almost always configure reverse DNS (and Forward-Confirmed reverse DNS, FCrDNS), residential broadband and mobile CGNAT pools frequently omit PTR records or return a generic pool hostname. Read our complete guide to Reverse DNS for troubleshooting steps.
Technical Specifications & Protocol Facts
Authoritative parameters, dimensions, and IETF RFC compliance
| Parameter / Dimension | Technical Specification | Standard / Authority |
|---|---|---|
| IPv4 Reverse Zone Format | Reversed dotted octets appended with .in-addr.arpa | RFC 1035 Section 3.5 |
| IPv6 Reverse Zone Format | 32 reversed hexadecimal nibbles appended with .ip6.arpa | RFC 3596 Section 2.5 |
| Queried Resource Record | PTR (Pointer Record, Type 12) with TTL in seconds | RFC 1035 |
| Pre-Query Guard | Flags RFC 1918 and RFC 6598 addresses before querying public DNS | RFC 6761 / RFC 6890 |
Frequently Asked Questions
Concise answers verified against IANA, APNIC, and IETF protocol standards
How does Reverse DNS (rDNS) convert an IPv4 address into a query name?
Reverse DNS reverses the order of the four IPv4 octets and appends .in-addr.arpa. For example, 8.8.8.8 becomes 8.8.8.8.in-addr.arpa, and 1.2.3.4 becomes 4.3.2.1.in-addr.arpa.
How is an IPv6 address formatted for a Reverse DNS ip6.arpa lookup?
The IPv6 address is first expanded to all 32 hexadecimal digits without :: compression. Every hex nibble is then reversed, separated by dots, and suffixed with .ip6.arpa.
Why do many residential broadband IPs return no PTR record?
ISPs are not required to publish PTR records for every dynamic residential or mobile CGNAT address. PTR records are primarily configured on mail servers, core routers, and cloud instances.
Related Network Tools & Technical Guides
Contextual utilities and reference documentation verified for this workflow
Diagnostic & Calculation Utilities
- DNS Lookup
Query A, AAAA, MX, TXT, NS, CNAME, and SOA records over DNS-over-HTTPS with TTL and status inspection.
- IP Address Lookup
Inspect country/region, ASN, provider, special-range scope, and data provenance for any IPv4 or IPv6 address.
- IP WHOIS / RDAP Lookup
Resolve the authoritative RIR via RFC 9224 IANA bootstrap and inspect structured RDAP allocation records.
Reverse DNS · Canonical: https://ipaddresslookup.in/reverse-dns-lookup · Reviewed: 2026-11-01
Reviewer: IPAddressLookup.in Technical Network Utility Group · Stateless Privacy · Accuracy & Data Limits