You’ve bought a dedicated IP, configured your SPF, DKIM, and DMARC, and your cold outreach is still landing in spam. Nine times out of ten, the culprit isn’t your content or your sending frequency—it’s a missing or misconfigured PTR record. This reverse DNS record is the quiet linchpin of email deliverability. Without it, even the most carefully crafted campaigns from a brand-new domain will bounce against strict filters at Gmail, Outlook, and Yahoo.
I’ve spent over 15 years managing sender reputations for agencies and B2B companies. In that time, I’ve seen dozens of clients tear their hair out over inbox placement, only to discover their PTR record pointed to a generic hostname like ip-203-0-113-42.ec2.internal instead of their sending domain. This one oversight can tank your deliverability, because every major mailbox provider performs a reverse DNS lookup on the connecting IP. If the hostname in that lookup doesn’t match your sending domain (or at least a subdomain you control), your email gets flagged as suspicious—or worse, silently dropped.
In this guide, I’ll walk you through what PTR records actually are, why they’re non-negotiable for cold email on a dedicated IP, and exactly how to set one up properly—with real-world examples and benchmarks. By the end, you’ll have a concrete checklist to fix your reverse DNS and start seeing those replies.
What Is a PTR Record, Really?
PTR (Pointer) records are the reverse of the more familiar A records. An A record maps a domain name to an IP address; a PTR record maps an IP address back to a domain name. This is called reverse DNS (rDNS).
When an email server receives a message, it logs the connecting IP. It then performs a PTR lookup on that IP to see what hostname it resolves to. That hostname is compared against the EHLO/HELO hostname your sending server presents, and sometimes against the domain in your From address. If there’s a mismatch—or worse, no PTR record at all—the receiving server applies a known spam signal.
Industry data backs this up. According to a 2023 survey by Spamhaus, over 80% of spam-filtering decisions incorporate reverse DNS checks. Mailbox providers like Google and Microsoft explicitly require PTR records for all inbound mail. If you send from an IP without a valid PTR, you’re essentially raising a red flag from the start.
Why Your Cold Email Campaign Needs a Dedicated IP (With Proper PTR)
If you’re doing serious cold outreach—hundreds or thousands of emails per day—you need a dedicated IP. Shared IPs are fine for low-volume transactional mail, but they’re risky for cold email because you share reputation with other senders. One spammy neighbor and your emails start getting throttled, regardless of your own engagement.
With a dedicated IP, you control your reputation. But that control comes with responsibility: you must build the reputation from scratch, and your infrastructure must be spotless. A correct PTR record is the first stone in that foundation. It establishes credibility and tells receivers you own the IP and the hostname associated with it.
Here’s the painful scenario I see too often: an agency buys a dedicated IP from a cloud provider like AWS or DigitalOcean. They spin up a mail server, configure SPF and DKIM, and start sending. But they forget to set the PTR record—or the provider’s default PTR is still active, pointing to something like ec2-203-0-113-42.compute-1.amazonaws.com. That generic hostname has zero correlation with your brand, and your deliverability suffers immediately.
The fix is straightforward: create a PTR record that maps your IP to a subdomain of your sending domain—for example, mail.yourdomain.com. This subdomain doesn’t need to exist as an A record; it just needs to be a valid hostname that you own. The receiving server will see that your IP identifies as mail.yourdomain.com, which matches your From domain and your SPF record. That alignment is a major trust signal.
How to Set Up a PTR Record for Your Dedicated IP
The process depends on where you bought or rent your IP. In most cases, you don’t create a PTR record directly in your DNS provider. Instead, you request a PTR record from your IP hosting provider—the company that actually owns the IP range (your VPS host, cloud provider, or dedicated server provider). They will then enter it into their reverse DNS zone, which is managed by the Regional Internet Registry (RIR).
Here are step-by-step instructions for the most common setups:
1. AWS (Amazon Web Services)
- Go to the EC2 Console and select your Elastic IP.
- Click “Actions” → “Manage reverse DNS.”
- Enter the hostname you want to use (e.g.,
mail.yourdomain.com). - If you’re using a VPC with internet gateway, AWS will automatically submit the PTR record to the RIR. If not, you may need to open a support ticket to request the PTR update.
2. DigitalOcean
- Log into the control panel and select your droplet.
- In the “Networking” tab, you’ll see a “Reverse DNS” section.
- Enter the FQDN (fully qualified domain name) you want, e.g.,
mail.yourdomain.com. - Ensure that an A record exists pointing that hostname to your droplet’s IP. DigitalOcean requires this before they’ll set the PTR.
3. Reliable or Dedicated Server Hosts (e.g., OVH, Hetzner)
- Log into your client area or control panel.
- Look for “IP Management” or “Reverse DNS.”
- Select the IP and enter the hostname.
- Confirm the change—often it’s instant, but some hosts take up to 24 hours to propagate.
Remember: your PTR hostname should match the hostname you use in your EHLO/HELO command on your mail server. Most mail servers default to something like localhost or the server’s fully qualified DNS name. You want that to be the same as your PTR.
Testing Your PTR Record
After setting up your PTR, you need to verify it. Use a simple command from a terminal:
dig -x 203.0.113.42
Replace the IP with your actual dedicated IP. The output should show your hostname in the answer section. You can also use online tools like MXToolbox’s Reverse Lookup. Additionally, run a full email deliverability test using a service like Mail-Tester.com—it will verify your PTR, SPF, DKIM, and DMARC alignment and give you a score out of 10. I recommend aiming for a perfect 10 before you send a single cold email.
Common PTR Mistakes That Kill Deliverability
Even experienced marketers trip over these. Avoid them at all costs:
1. Using a Generic rDNS Name
If your PTR returns ip-203-0-113-42.ec2.internal, that's a dead giveaway to Gmail that you’re a random cloud instance. The hostname must be related to your domain. A generic name fails the “matching hostname” check and often triggers a spam block.
2. Mismatch Between PTR, EHLO, and From Domain
Your PTR hostname (mail.yourdomain.com), your EHLO greeting (e.g., mail.yourdomain.com), and your From domain (@yourdomain.com) should all share the same root domain. If they don’t align, you break the reputation chain.
3. Setting PTR on a Subdomain That Sends Nothing
Make sure the subdomain you use in the PTR is actually the one you’re sending from. If you have send.yourdomain.com for your transactional emails and you’re using it for cold outreach too, the PTR should point to that same subdomain. If you’re using a different sending subdomain, your PTR should match that one.
4. Forgetting to Update PTR When Changing IP
When you migrate to a new dedicated IP, you must update the PTR immediately. I’ve seen agencies forget to do this and wonder why their carefully built reputation crashes overnight.
Does a PTR Record Alone Guarantee Inbox Placement?
No—but it’s the prerequisite. Without it, you’re running uphill. With it, you still need to earn engagement, keep spam complaints below 0.1%, and warm up your IP gradually. But a correct PTR is the difference between being considered a legitimate sender and being part of the “probably spam” pile from the first handshake.
Another crucial piece: IP warming. Even with a pristine PTR, a brand-new dedicated IP has zero reputation. You need to ramp up sending volume over a few weeks, starting with your most engaged contacts. Tools like FiresideSender automate this warming process by sending tiny batches to mailbox providers incrementally, helping build a positive history without alerting spam filters. Combining FiresideSender’s AI-driven warming with a perfectly configured PTR is the fastest path to consistent inbox placement.
Actionable Checklist for Your Next Campaign
Before you hit send on that cold outreach sequence, run this checklist:
- ☐ Your dedicated IP is assigned, and you’ve requested a PTR record from your host that points to a subdomain of your sending domain (e.g.,
mail.yourdomain.com). - ☐ Your mail server’s EHLO hostname is set to that same subdomain.
- ☐ You’ve verified the PTR record with
dig -xand it returns the correct hostname. - ☐ Your SPF record includes your dedicated IP address, and DKIM is aligned with your From domain.
- ☐ You have a DMARC policy that doesn’t quarantine—at least during the initial warming phase.
- ☐ You’re using an IP warming scheduler (like FiresideSender) to gradually increase volume over 2–4 weeks.
Once this is all in place, run a Mail-Tester test. If you score 10/10, you’re ready to start scaling. If not, dig into the report—it will pinpoint exactly where the misconfiguration lies.
The Bottom Line: PTR Is Non-Negotiable
You wouldn’t drive a race car without a steering wheel. Similarly, you shouldn’t send cold emails from a dedicated IP without a correct PTR record. It’s the baseline infrastructure that every serious mailbox provider checks. Fixing this one oversight takes less than an hour and can improve your deliverability by a 30–50% margin overnight—I’ve seen it happen repeatedly.
So stop wrestling with spam filters. Invest the time to set up your reverse DNS properly, align your infrastructure, and let your content and offer do the heavy lifting. Your future replies are waiting on the other side of a correctly configured PTR record.