If you’ve ever wondered why your perfectly written emails end up in a spam folder, or why your mail server gets flagged during an SMTP test, there’s a good chance a DNS PTR record is at the heart of the issue. This guide breaks down everything you need to know about PTR records: what they are, how they work, why they matter, and how to check, create, and troubleshoot them.
What Is a DNS PTR Record?
A DNS PTR record (short for Pointer record) is a type of DNS record that maps an IP address back to a domain name. It is essentially the reverse of an A record, which maps a domain name to an IP address.
Think of it this way: the regular DNS system works like a phonebook where you look up a name to find a number. A PTR record works like a reverse phonebook; you start with the number (IP address) and look up who it belongs to (domain name). This process is called a reverse DNS lookup (or rDNS).
Simple definition: A DNS PTR record answers the question: “What domain name is associated with this IP address?”
PTR records are not used for general website browsing. Instead, they play a critical behind-the-scenes role in email delivery, network security, server logging, and spam prevention.
PTR Record vs. A Record: What Is the Difference?
Understanding a PTR record becomes easy once you compare it with the DNS A record, which most website owners are already familiar with.
| Feature | A Record | PTR Record |
| Direction | Domain → IP address | IP address → Domain |
| Lookup type | Forward DNS lookup | Reverse DNS lookup |
| Where it’s stored | Your domain’s DNS zone | Reverse DNS zone (.in-addr.arpa) |
| Who controls it | Domain owner | IP address owner (ISP or hosting provider) |
| Primary use | Website resolution | Email verification, logging, and security |
Example:
- A record: mail.example.com → 192.0.2.10
- PTR record: 192.0.2.10 → mail.example.com
Both records should point to each other. When they do, this is called Forward-Confirmed reverse DNS (FCrDNS), and it is a key trust signal for email servers.
How Does a DNS PTR Record Work?
Here is a step-by-step breakdown of how a PTR record lookup works:
- A mail server receives an incoming email from IP address 192.0.2.10.
- To verify the sender’s identity, the receiving server performs a reverse DNS lookup on 192.0.2.10.
- The DNS system looks up the PTR record for the reverse IP address 10.2.0.192.in-addr.arpa.
- The PTR record returns the associated domain name: mail.example.com.
- The receiving server then does a forward DNS lookup on mail.example.com to confirm it points back to 192.0.2.10.
- If both lookups match, the server accepts the email as coming from a legitimate, verified source.
If the PTR record is missing, mismatched, or misconfigured, the receiving server may reject or flag the email as spam.
What Is a Reverse DNS Lookup?
A reverse DNS lookup is the process of resolving an IP address into its associated domain name, using the PTR record stored in the DNS system.
It is the exact opposite of a standard (forward) DNS lookup:
- Forward DNS lookup: You type example.com into your browser → DNS returns 192.0.2.1
- Reverse DNS lookup: You query IP 192.0.2.1 → DNS returns example.com
Reverse DNS lookups are used for:
- Email verification: to confirm the identity of a sending mail server
- Security auditing: to map IP addresses found in network logs to human-readable domain names
- Spam filtering: to check whether the sending IP is associated with a known, legitimate domain
- Network troubleshooting: to identify the source of traffic or connections in server logs
You can run a reverse DNS lookup instantly using the HasheTools DNS Reverse Lookup Tool. Just enter any IP address and get the PTR record result in seconds.
PTR Record Format Explained (IPv4 and IPv6)
The way PTR records are stored in DNS is a bit different from how you might expect. The IP address is written backwards, and a special domain suffix is appended.
IPv4 PTR Record Format
For an IPv4 address like 192.0.2.255, the PTR record is stored as:
255.2.0.192.in-addr.arpa
The IP octets are reversed, and .in-addr.arpa is appended. This naming convention exists because DNS domains are organized from most specific (left) to most general (right), and reversing the IP address preserves this hierarchical structure.
IPv6 PTR Record Format
IPv6 PTR records work the same way but are more complex. For the IPv6 address 2001:db8::1, the PTR record is stored under:
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa
The IPv6 address is fully expanded, reversed digit by digit, and .ip6.arpa is appended instead of .in-addr.arpa.
What Is .arpa and Why Is It Used?
The .arpa top-level domain is a special domain used for managing network infrastructure in DNS. It is the oldest top-level domain on the internet, named after ARPA (Advanced Research Projects Agency), which created ARPANET, the precursor to the modern internet. The subdomain in-addr. arpa is specifically reserved for reverse DNS lookups of IPv4 addresses.
What Is FCrDNS (Forward-Confirmed Reverse DNS)?
FCrDNS stands for Forward-Confirmed reverse DNS, sometimes also called Full-Circle reverse DNS. It is a verification process that checks whether a PTR record and an A record are consistent with each other.
Here is how FCrDNS verification works:
- A reverse DNS lookup is performed on an IP address – it returns a domain name via the PTR record.
- A forward DNS lookup is then performed on that domain name – it should return the original IP address.
- If both match, the FCrDNS check passes, and the IP and domain are legitimately associated.
Why does FCrDNS matter?
FCrDNS is used by many email servers and security systems as a trust signal. A passing FCrDNS check indicates that:
- The domain owner and IP address owner are the same entity (or at least aware of each other)
- The server is operating transparently and following internet best practices
- The email is much less likely to be spam
If your PTR record exists but your A record does not point back to the same IP, FCrDNS will fail, and your emails may still be treated as suspicious.
Why Does a PTR Record Matter?
You might be thinking: “I don’t run a mail server, do I even need a PTR record?” For most regular website owners and users, PTR records operate entirely in the background. But if you fall into any of the following categories, they are critical:
1. Email Deliverability
This is the biggest use case. Mail servers at Gmail, Outlook, Yahoo, and other providers routinely perform reverse DNS lookups on every incoming email. If your sending IP has no PTR record, or a mismatched one, your emails are at high risk of being rejected or routed straight to spam. This is especially true for businesses running their own mail servers.
2. Anti-Spam Filtering
Spam filters assign a “spam score” to incoming emails based on dozens of signals. A missing or mismatched PTR record is a significant negative signal. Most enterprise anti-spam systems (including SpamAssassin) actively penalize emails from IPs with no reverse DNS.
3. Server Logging and Network Monitoring
System logs often record only IP addresses. When administrators need to investigate traffic, security incidents, or network activity, PTR records allow them to translate those raw IP addresses into readable domain names, making troubleshooting and forensic analysis far easier.
4. Server Identity and Trust
When servers connect, not just for email, but for other protocols, PTR records are used to verify the identity of the connecting server. This is a fundamental layer of trust in the internet infrastructure.
5. Cybersecurity Investigations
Security researchers, penetration testers, and network analysts use PTR lookups as part of reconnaissance and investigation workflows. Knowing which domain is associated with a given IP helps identify malicious actors, trace attack origins, and map network infrastructure.
PTR Records and Email Deliverability
Email deliverability is where PTR records have the most direct, visible impact. Here is a detailed look at how they affect your email:
How Receiving Mail Servers Use PTR Records
When an email arrives, the receiving mail server performs the following sequence:
- It checks the sender’s IP address.
- It performs a reverse DNS lookup to find the PTR record for that IP.
- It checks whether the PTR record resolves to a domain name.
- It performs a forward lookup on that domain name to confirm it matches the original IP (FCrDNS check).
- It compares the result against the SMTP banner that the sending server presented.
If any of these steps fail, no PTR record, wrong domain, mismatched A record, or SMTP banner mismatch, the email may be rejected, quarantined, or marked as spam.
Related read: Reverse DNS Does Not Match SMTP Banner
PTR Records and Spam Filters
Many popular anti-spam systems, including those used by major email providers, use reverse DNS as a filtering criterion:
- No PTR record = high suspicion of spam
- Generic PTR (e.g., ip-192-0-2-10.hosting.example.com) = moderate suspicion
- Properly configured PTR pointing to your domain = trust signal
PTR Records and Email Authentication (SPF, DKIM, DMARC)
PTR records work alongside, but are separate from, SPF, DKIM, and DMARC. While those protocols authenticate the email content and domain, PTR records authenticate the sending server’s IP address. Together, they form a comprehensive email authentication stack.
PTR Records vs. Other DNS Record Types
Here is how PTR records compare to other common DNS record types:
| Record Type | Function | Direction |
| A record | Map the domain to an IPv4 address | Forward (domain → IP) |
| AAAA record | Maps the domain to an IPv6 address | Forward (domain → IPv6) |
| PTR record | Maps an IP address to a domain | Reverse (IP → domain) |
| CNAME record | Aliases one domain to another | Forward (domain → domain) |
| MX record | Specifies the mail server for a domain | Forward (domain → mail server) |
| TXT record | Stores text data (SPF, DKIM, DMARC, etc.) | N/A |
| SOA record | Stores administrative info about a DNS zone | N/A |
Related read: DNS Records for google.com Explained
How to Check a PTR Record
There are several ways to check the PTR record for an IP address.
Method 1: Use HasheTools DNS Reverse Lookup
The easiest method is to use the HasheTools DNS Reverse Lookup Tool:
- Go to hashetools.com/tools/dns-reverse
- Enter the IP address you want to look up
- Click “Lookup”
- The tool will return the PTR record (domain name) associated with that IP
Method 2: Use the nslookup Command
On Windows, macOS, or Linux, open a terminal or command prompt and run:
nslookup 192.0.2.10
Or for a more targeted reverse lookup:
nslookup -type=PTR 10.2.0.192.in-addr.arpa
Method 3: Use the dig Command (Linux/macOS)
dig -x 192.0.2.10
The -x flag tells dig to perform a reverse lookup automatically. Look for the ANSWER SECTION in the output; it will show the PTR record.
Method 4: Use HasheTools SMTP Test
If you want to check PTR records specifically for your mail server and verify FCrDNS, use the HasheTools SMTP Test Tool. It will flag any PTR mismatches and SMTP banner issues automatically.
How to Create or Set Up a PTR Record
This is where PTR records differ significantly from all other DNS records. You cannot create a PTR record in your domain’s DNS settings (e.g., in Cloudflare, Namecheap, or GoDaddy). PTR records are controlled by whoever owns the IP address block, typically your ISP or hosting provider.
Step-by-Step: Setting Up a PTR Record
Step 1: Find your mail server’s IP address
Log in to your hosting control panel or run nslookup mail.yourdomain.com to find the IP address of your mail server.
Step 2: Identify who controls that IP
- If you host on a VPS or dedicated server (e.g., AWS, DigitalOcean, Vultr, Linode), the cloud provider controls the reverse DNS.
- If you use a shared hosting plan, your hosting company controls it.
- If you have a direct ISP-allocated IP range, your ISP controls it.
Step 3: Contact your provider or use their control panel
Many modern cloud providers allow you to set PTR records directly:
- AWS: Go to EC2 > Elastic IPs > Edit reverse DNS
- DigitalOcean: Rename your Droplet to the full hostname. DigitalOcean automatically creates the PTR record
- Vultr: Go to your server’s settings and find “Reverse DNS.”
- Linode/Akamai: Network tab > Reverse DNS
- Shared hosting: Submit a support ticket with your hosting provider
Step 4: Enter the correct PTR value
The PTR record value should be the fully qualified domain name (FQDN) of your mail server, for example: mail.yourdomain.com
Step 5: Create the matching A record
Make sure that mail.yourdomain.com has an A record pointing back to the same IP address. This completes the FCrDNS configuration.
Step 6: Verify the PTR record
After the DNS propagation period (usually 15 minutes to a few hours), verify the PTR record using the HasheTools DNS Reverse Lookup or the dig -x command.
Common PTR Record Mistakes and How to Fix Them
Mistake 1: Missing PTR Record
Symptom: Emails are being rejected or going to spam. SMTP tests show “No PTR record found.”
Fix: Contact your hosting provider or ISP and request a PTR record for your mail server’s IP address.
Mistake 2: Generic or Default PTR Record
Symptom: Your PTR record resolves to something like ip-192-0-2-10.us-east-1.compute.internal instead of your domain.
Fix: Update the PTR record via your cloud provider’s control panel (see the setup steps above) to point to your actual mail server hostname.
Mistake 3: PTR Record and A Record Mismatch (FCrDNS Failure)
Symptom: PTR record exists but FCrDNS check fails. The domain in your PTR record does not have a matching A record pointing back to the IP.
Fix: Ensure that the domain name in your PTR record has a corresponding A record pointing to the correct IP. Both records must match.
Mistake 4: SMTP Banner Mismatch
Symptom: SMTP test shows “Reverse DNS does not match SMTP banner.”
Fix: Update your mail server’s hostname (the value in the SMTP greeting/banner) to match the domain in your PTR record. In Postfix, this is the myhostname setting in /etc/postfix/main.cf.
Related read: Reverse DNS Does Not Match SMTP Banner
Mistake 5: Multiple PTR Records for One IP
Symptom: Inconsistent reverse lookups; some tools return different results.
Fix: Only one PTR record should exist per IP address. Remove any duplicates.
Mistake 6: Using a Dynamic IP Address
Symptom: PTR record keeps becoming invalid as the IP changes.
Fix: PTR records should only be used with static IP addresses. If your server has a dynamic IP, request a static IP from your provider before configuring a PTR record.
PTR Record Best Practices
Follow these guidelines to ensure your PTR records are configured correctly and deliver maximum benefit:
- Always configure a PTR record for every mail server IP. This is considered a basic Internet standard for email servers. Missing PTR records are a major red flag for spam filters.
- Make the PTR record match your mail server’s SMTP banner. The hostname your mail server announces when connecting to other servers must match what your PTR record resolves to.
- Ensure FCrDNS passes. Your PTR record should resolve to a domain, and that domain’s A record must point back to the same IP. Both lookups must agree.
- Use a meaningful, domain-specific hostname. Instead of a generic hostname, use something like mail.yourdomain.com. This builds trust and is easier to recognize in logs.
- Use only one PTR record per IP. Multiple PTR records for a single IP create ambiguity and can cause inconsistent behavior.
- Only use static IPs for PTR records. Dynamic IP addresses change over time, making PTR records unreliable.
- Regularly audit your PTR records. Use tools like HasheTools DNS Reverse Lookup to periodically check that your PTR records are correct and still match your A records.
- Keep TTL values reasonable. A TTL of 300–3600 seconds is standard for PTR records. Too high a TTL means changes propagate slowly; too low may cause unnecessary DNS query load.
Frequently Asked Questions
Do I need a PTR record for my website?
Not necessarily. PTR records are primarily needed for mail servers. If you only run a website and use a third-party email provider (like Google Workspace or Microsoft 365), those providers handle PTR records on your behalf. You only need to configure PTR records yourself if you operate your own mail server.
Who controls PTR records?
PTR records are controlled by the owner of the IP address block, not the domain owner. This is typically your ISP, cloud provider, or hosting company. To set up a PTR record, you must contact whoever issued your IP address.
Can I have multiple PTR records for one IP?
It is technically possible but strongly discouraged. Best practice is to have exactly one PTR record per IP address. Multiple PTR records create ambiguity and can confuse mail servers and spam filters.
What happens if my PTR record is missing?
If your mail server has no PTR record, many receiving mail servers will reject your emails outright or deliver them to the spam folder. It is one of the most impactful configuration issues for email deliverability.
How long does it take for a PTR record to propagate?
PTR record changes typically propagate within 15 minutes to a few hours, depending on the TTL set by your provider and the caching behavior of DNS resolvers worldwide.
What is the difference between a PTR record and reverse DNS?
They are closely related. Reverse DNS is the process of resolving an IP address to a domain name. A PTR record is the specific DNS resource record that makes reverse DNS possible. In other words, PTR records are the mechanism by which reverse DNS lookups are answered.
Can I check someone else’s PTR record?
Yes. You can perform a reverse DNS lookup on any public IP address using HasheTools DNS Reverse Lookup or command-line tools like dig -x or nslookup.
Is a PTR record the same as an rDNS record?
Yes. PTR record and rDNS record are the same thing. “rDNS” stands for reverse DNS, and the PTR (Pointer) record is the DNS record type used to enable reverse DNS lookups.
Conclusion
A DNS PTR record is a small but powerful piece of internet infrastructure. While regular users never interact with it directly, it plays an essential role in email deliverability, spam prevention, server logging, and network security.
If you run a mail server, a missing or misconfigured PTR record can silently destroy your email deliverability, causing your messages to be rejected or flagged as spam by major providers like Gmail, Outlook, and Yahoo. Getting your PTR record right and ensuring FCrDNS passes is one of the most effective steps you can take to protect your sender reputation.
Ready to check your PTR record right now? Use the HasheTools DNS Reverse Lookup Tool to instantly look up the PTR record for any IP address and verify that your reverse DNS is configured correctly.
