What Is Reverse DNS? How Reverse DNS Lookup Works and Why It Matters
Normal DNS answers the question: what IP address does this name point to? Reverse DNS answers the mirror image: what name does this IP address point to? It seems like a curiosity until the day your outgoing email starts disappearing into spam folders — because reverse DNS is one of the quiet checks that mail servers run on every message they receive.
Here is how it works, how to check it, and when you actually need to care.
Forward vs Reverse: What Are the Two Directions of DNS?
A forward lookup starts with a name. You type domain360.site, DNS returns an IP address, your browser connects. This is the direction everything on the web uses.
A reverse lookup starts with an IP address. Given 203.0.113.10, reverse DNS asks the system what hostname is registered for it. The answer comes from a PTR record — a pointer record — stored in a special DNS zone built from the IP address written backwards under the in-addr.arpa domain. You never need to touch that machinery directly, but it explains an important quirk: PTR records live with whoever owns the IP address, which is almost never you.
That means your hosting provider, VPS company, or ISP controls your reverse DNS — not your domain registrar, and not your DNS host. Changing a PTR record happens in your hosting panel or through a support ticket, never in the same place you manage A records and MX records.
How Do You Run a Reverse DNS Lookup?
The commands mirror the forward lookups covered in our DNS lookup commands guide.
With nslookup, just pass the IP: nslookup 8.8.8.8 — which returns dns.google, the hostname Google registers for its resolver.
With dig, use the -x flag: dig -x 8.8.8.8 — same answer with fuller detail.
Three results are possible. A hostname comes back: the IP has a PTR record. Nothing comes back: no reverse DNS is configured for that IP. A generic hostname comes back — something like 203-0-113-10.static.yourhost.com: the provider has an automatic placeholder record, which is common on cheap hosting and unassigned IPs.
Why Does Reverse DNS Decide Email Deliverability?
This is the section that matters for anyone running their own mail server or sending email from a VPS.
When your server connects to Gmail, Outlook, or any receiving mail server to deliver a message, the receiver sees your IP address before anything else. Before reading a single line of your email, many receivers run a reverse lookup on that IP and apply a simple logic. No PTR record at all: high spam suspicion — many servers reject the connection outright. Generic provider PTR record: moderate suspicion — a real mail operator would have configured a proper hostname. PTR record that matches the hostname your server announces, with a forward lookup on that hostname resolving back to the same IP: the trust check passes.
That last condition is called forward-confirmed reverse DNS, and it is the standard you want to meet: IP resolves to mail.yourdomain.com, and mail.yourdomain.com resolves back to the same IP. Set the PTR through your hosting provider, set the matching A record in your normal DNS, and the loop closes.
Reverse DNS works alongside the TXT-record trio of SPF, DKIM, and DMARC. Getting all of them right is what separates mail that arrives from mail that silently vanishes. And remember that all of it depends on the domain itself staying registered — an expired domain takes your entire email identity down with it, as our guide on domain expiry and email explains.
How Is Reverse DNS Used as a Research Tool?
Beyond email, reverse DNS earns its keep in investigation work.
Identifying who is behind an IP. Server logs full of requests from an unknown IP? A reverse lookup often names the operator — crawl-66-249-66-1.googlebot.com identifies Googlebot, while a bare IP with no PTR from a random network suggests a scraper worth blocking.
Verifying claimed crawlers. Anyone can send a user-agent string claiming to be Googlebot. The reliable verification is reverse DNS: look up the IP, confirm the hostname ends in googlebot.com or google.com, then forward-resolve that hostname and confirm it returns the same IP. Fake crawlers fail this loop.
Mapping infrastructure during due diligence. When researching a domain purchase or investigating a suspicious site, reverse DNS on the site IP can reveal the hosting provider and sometimes neighbouring hostnames on the same server — context that pairs well with the ownership methods in our guide on how to find who owns a domain.
How Do You Set Up Reverse DNS? The Short Version
If you send email from your own server, the checklist is brief. Decide your mail hostname, such as mail.yourdomain.com. Create the forward A record pointing that hostname at your server IP in your normal DNS. Set the PTR record for the IP to the same hostname — in your hosting control panel if offered, otherwise via a support ticket. Verify the loop with dig -x on your IP and a forward lookup on the hostname. Most providers apply PTR changes within hours.
If you use Google Workspace, Microsoft 365, or any hosted email service, skip all of this — their sending IPs carry their reverse DNS, and there is nothing for you to configure.
Reverse DNS is one of those pieces of domain infrastructure that works silently until it does not. Check it once, set it correctly, and it joins the list of things — like expiry dates watched by a domain management dashboard — that quietly never cause you a problem again.
Quick Answers
Never lose a domain again
Track every domain you own in one dashboard. Free for up to 15 domains.