Your emails are bouncing or landing in spam, and somewhere in a support ticket or forum, someone tells you to "set up your CNAME records." You nod, close the tab, and move on because it sounds like something only engineers care about.
Here's the thing: CNAME records are one of the three things that actually matter for email deliverability in 2026. And if you're sending cold emails at any real volume - 50+ per day, 500+ per week - getting this wrong will kill your entire campaign before it starts.
This guide walks you through what CNAME records are, why they matter for cold email, and exactly how to set them up so your emails actually land in inboxes.
What a CNAME Record Actually Does (And Why It Matters for Cold Email)
A CNAME record - Canonical Name record - is a DNS entry that points one domain name to another. In cold email, you use CNAME records to authenticate your sending domain to email service providers and mailbox providers like Gmail and Outlook.
Here's why this matters: When you send an email from your domain, Gmail doesn't just check if the email looks legitimate. It checks your domain's reputation using SPF, DKIM, and DMARC records. CNAME records are how you connect these authentication methods to your actual email sending infrastructure.
Without proper CNAME setup, mailbox providers see your emails as coming from an unverified source. That means spam folder. Or worse - bounce.
The practical impact: campaigns with proper CNAME records see 15-20% better inbox placement than campaigns without them. That's the difference between 80 emails landing and 100 emails landing in a 500-email week.
The Three CNAME Records You Actually Need
You don't need to set up a hundred different CNAME records. You need three specific ones for cold email to work well.
1. CNAME for DKIM Signing
DKIM (DomainKeys Identified Mail) is a cryptographic signature that proves your emails came from you. Your email service provider gives you a CNAME record that points to their DKIM signing server.
In most email platforms (Lemlist, Instantly, Apollo, etc.), you'll see something like this in your domain settings:
default._domainkey.yourdomain.com CNAME default._domainkey.sendingservice.com
That CNAME tells Gmail and Outlook: "When you see an email signed with this DKIM key, trust that it came from yourdomain.com."
2. CNAME for Tracking (Optional But Recommended)
Most cold email platforms offer click and open tracking. They use CNAME records to track these events without harming your sender reputation.
Example setup:
track.yourdomain.com CNAME track.sendingservice.com
This lets you know who opened your email and who clicked links without raising spam flags. It also keeps your domain's reputation intact because the tracking happens through your own subdomain, not the service's.
3. CNAME for DMARC Reporting (Advanced)
DMARC (Domain-based Message Authentication, Reporting and Conformance) is the policy layer that tells mailbox providers what to do if an email fails authentication. Some platforms provide CNAME records for DMARC aggregate reports.
This is less critical for cold email than DKIM, but it gives you visibility into how your domain is being used across the internet.
How to Actually Set Up Your CNAME Records
Step 1: Get the CNAME Details From Your Email Platform
Log into your cold email platform (Lemlist, Instantly, Apollo, whatever you're using). Go to settings - usually called "Domain Settings" or "Email Authentication" or "Deliverability."
You'll see something like:
Name: default._domainkey.yourdomain.com Value: default._domainkey.sendingservice.com Type: CNAME
Copy these exact values. Don't change them. Don't try to "improve" them.
Step 2: Access Your Domain Registrar or DNS Provider
Log into GoDaddy, Namecheap, Route53, Cloudflare - wherever your domain's DNS is hosted. This is usually the place you bought your domain.
If you don't know where your DNS is, open a terminal and run:
dig NS yourdomain.com
That tells you who manages your DNS.
Step 3: Add the CNAME Record
In your DNS provider, find the option to add a new record (usually called "Add Record" or "Create Record").
Fill in:
- Type: CNAME
- Name: default._domainkey (just the subdomain part, not the full domain)
- Value: default._domainkey.sendingservice.com (paste exactly what your email platform gave you)
- TTL: Leave as default, usually 3600
Click save.
Step 4: Verify in Your Email Platform
Go back to your email platform and click "Verify" or "Check DNS." Most platforms have a button that confirms your CNAME is set up correctly.
This usually takes 15 minutes to a few hours to propagate through the internet. If it doesn't verify immediately, wait an hour and try again.
Common CNAME Setup Mistakes That Kill Your Deliverability
Mistake 1: Using your root domain instead of a subdomain. Your root domain (yourdomain.com) should use an A or MX record, not a CNAME. Always use a subdomain like default._domainkey.yourdomain.com.
Mistake 2: Copying the CNAME value but forgetting the subdomain part. The CNAME consists of two parts: the "Name" (what you're creating) and the "Value" (where it points). People often paste both into the same field.
Mistake 3: Setting up CNAME records but skipping SPF and DKIM. CNAME records only work if your SPF and DKIM authentication is already correct. If those aren't set up, CNAME alone won't save you. Check our cold email deliverability guide for the full authentication stack.
Mistake 4: Setting up one CNAME and thinking you're done. Most platforms need at least two CNAME records: one for DKIM signing and one for tracking. Read your platform's documentation carefully.
How to Check if Your CNAME Records Are Actually Working
After you set up your CNAME records, verify them with a DNS checker:
- Go to MXToolbox.com or DNSChecker.org
- Enter your full subdomain (default._domainkey.yourdomain.com)
- Run a CNAME lookup
- You should see it resolve to the value your email platform gave you
If it shows "No records found" after waiting an hour, go back to your DNS provider and check that you saved the record correctly.
Once your CNAMEs are verified, send a test email to a Gmail account and check if it lands in the inbox. If it's still going to spam after CNAME, SPF, and DKIM are all correct, you might have a sender reputation issue - that's a separate problem covered in our sender reputation guide.
CNAME Records in 2026: What's Changed
In 2026, mailbox providers are more strict about authentication than ever. Gmail's 2024 requirements for unauthenticated bulk senders forced most legitimate cold email platforms to tighten their own standards.
This means CNAME records went from "nice to have" to "necessary." Any platform worth using will require you to set them up. If a cold email tool doesn't ask you to configure CNAME records, it's probably not a platform you should trust with your domain reputation.
The Gap Between Knowing This and Running It Well
Setting up CNAME records takes 15 minutes. But doing it right - ensuring they're set up correctly, verifying they propagate, monitoring them over time, and integrating them into a broader email infrastructure - is where most people stumble.
When you're running campaigns at scale (200+ emails per day across multiple domains), you need someone managing your DNS, monitoring your authentication, catching issues before they tank your deliverability, and handling the 20 little things that break along the way. That's the difference between knowing what a CNAME record is and actually maintaining a cold email operation that consistently lands emails in inboxes. If you'd rather not manage this yourself, that's what BEC Growth handles - the infrastructure piece that lets you focus on reply management and closing deals.