Reverse DNS Lookup
Enter an IPv4 address to find its PTR record — the hostname registered by the IP owner.
What Is Reverse DNS Lookup?
Standard DNS lookup translates a domain name into an IP address. Reverse DNS lookup does the opposite — it resolves an IP address back to its associated hostname. This is done by querying a special DNS zone called in-addr.arpa (for IPv4) using a record type called PTR (Pointer).
For example, a reverse DNS lookup on 8.8.8.8 returns dns.google — revealing that this IP is Google's public DNS resolver. The lookup works by reversing the IP (8.8.8.8 → 8.8.8.8.in-addr.arpa) and querying for the PTR record stored there.
Reverse DNS Lookup Commands
You can perform reverse DNS lookups directly from your terminal on any operating system using the built-in nslookup, dig, or host commands.
nslookup 8.8.8.8Reverse lookup — nslookup auto-handles in-addr.arpa
nslookup 8.8.8.8 1.1.1.1Use Cloudflare as the resolver instead of your ISP
dig -x 8.8.8.8Full PTR record output with TTL and authority section
dig -x 8.8.8.8 +shortShort output — returns just the hostname
dig PTR 8.8.8.8.in-addr.arpaManual query — explicitly targets the PTR record
host 8.8.8.8Simplest format — returns 'domain name pointer hostname'
host 1.1.1.1 8.8.8.8Use Google DNS as the resolver
How PTR Records and in-addr.arpa Work
When a Regional Internet Registry (ARIN, RIPE, APNIC, etc.) assigns an IP block to an ISP, it also delegates the corresponding in-addr.arpa zone. The ISP then manages PTR records for their IP ranges. For example, if Comcast owns the block 75.70.0.0/16, it controls the DNS zone 0.70.75.in-addr.arpa and can set PTR records for every IP in that block.
IPv6 reverse DNS uses the ip6.arpa zone. An IPv6 address like 2001:4860:4860::8888 is expanded to its full 32-nibble form, reversed, and queried under ip6.arpa.
Common Use Cases for Reverse DNS
Mail servers check PTR records to verify sender legitimacy. Missing or mismatched rDNS causes emails to fail spam filters or be rejected outright.
Identify who owns an IP connecting to your server — whether it's Googlebot, a known CDN, or an unknown hosting provider.
Trace the source of traffic, verify BGP routes, and investigate server logs by resolving IP addresses to meaningful hostnames.
Determine if a suspicious IP belongs to a legitimate ISP, a cloud provider, a known data center, or a residential user.
DNSBL blacklists and spam filters check rDNS records as part of IP reputation scoring — IPs without PTR records receive lower trust scores.
Convert raw IP addresses in server logs into readable hostnames for easier analysis and attribution in SIEM tools.
Frequently Asked Questions
What is a reverse DNS lookup?
A reverse DNS (rDNS) lookup is the process of resolving an IP address back to its associated hostname (domain name). Standard DNS lookup goes domain → IP; reverse DNS goes IP → domain. The result comes from a PTR (Pointer) record stored in the special 'in-addr.arpa' DNS zone. Example: querying 8.8.8.8 returns dns.google.
What is a PTR record?
A PTR (Pointer) record is the DNS record type used for reverse DNS lookups. It maps an IP address to a hostname and is stored in a special reverse zone: for IPv4 address 1.2.3.4, the PTR query goes to 4.3.2.1.in-addr.arpa. PTR records must be created by the IP owner (usually the ISP or hosting provider) — not the domain owner.
How do I do a reverse DNS lookup with nslookup?
On Windows, open Command Prompt and run: nslookup 8.8.8.8 — nslookup automatically handles the in-addr.arpa conversion. On macOS/Linux you can also run: nslookup 8.8.8.8. The result shows the PTR record in the 'name' field. To query a specific DNS server: nslookup 8.8.8.8 1.1.1.1
How do I do a reverse DNS lookup with dig?
On macOS and Linux, use the dig -x flag: dig -x 8.8.8.8 — the -x flag automatically reverses the IP and queries the in-addr.arpa zone. The PTR record appears in the ANSWER SECTION. For a short output: dig -x 8.8.8.8 +short — this returns just the hostname.
How do I do a reverse DNS lookup on Ubuntu/Linux?
On Ubuntu and most Linux distributions, use either: dig -x [IP ADDRESS] or: host [IP ADDRESS]. Example: dig -x 1.1.1.1 returns 'one.one.one.one'. The 'host' command gives a simpler output: host 8.8.8.8 returns 'dns.google'. Both tools are available in the dnsutils package (sudo apt install dnsutils).
Why does an IP have no reverse DNS record?
Not all IP addresses have PTR records. This is common for: residential/dynamic IPs (ISPs often use generic hostnames like pool-100-20-40.verizon.net or none at all), newly provisioned cloud/VPS servers (PTR must be configured by the hosting provider), and some legacy IP blocks. A missing PTR record can cause email delivery issues — many mail servers reject messages from IPs without valid reverse DNS.
What is the in-addr.arpa zone?
The in-addr.arpa zone is a special DNS zone used for IPv4 reverse lookups. The IP is reversed and '.in-addr.arpa' is appended: IP 1.2.3.4 becomes the DNS query 4.3.2.1.in-addr.arpa. For IPv6, the equivalent zone is ip6.arpa, where the address is expanded and fully reversed in nibble format. The RIR (ARIN, RIPE, APNIC, etc.) delegates sub-zones of in-addr.arpa to ISPs when assigning IP blocks.
Can I set up reverse DNS for my IP address?
Yes, but only the IP block owner can create PTR records. For residential ISPs, contact your provider — some (like Comcast Business) allow PTR record requests. For cloud/VPS hosting (AWS, DigitalOcean, Azure), you can configure PTR records in your provider's dashboard. For your own IP block (if you have PI space), you manage the reverse zone yourself through your RIR account.
Related Tools & Resources
Query A, AAAA, MX, TXT, NS, CNAME records for any domain.
Find ISP, ASN, and geolocation for any IP address.
Query IP block and domain registration data.
See your current public IP, ISP, and reverse DNS hostname.
A complete guide to the DNS resolution process.
Why DNS leaks expose your real IP even behind a VPN.