
DNS and Email: Why DNS Is Essential for Email Deliverability
When an email is sent, it does not travel directly from sender to inbox. Behind the scenes, DNS supports routing and authentication checks that can affect delivery.
Poorly configured DNS records can cause email authentication or routing problems.
Let's break down the role of DNS in email deliverability.
Key Takeaways
- DNS supports email routing and authentication.
- MX routes incoming mail; SPF, DKIM, and DMARC address different authentication identities.
- Test real sending services after DNS changes, rather than relying on a DNS lookup alone.
What Is DNS? (In Simple Terms)
DNS (Domain Name System) is the internet’s address book. It translates human-readable domains (like example.com) into technical instructions that servers understand
For email, DNS tells the receiving mail server:
- Which servers are allowed to send mail for a domain
- How to verify that a message is authentic
- What to do if authentication fails
For email, DNS supplies information used for routing and authentication checks.
Why DNS Matters for Email Deliverability
Mailbox providers like Gmail, Outlook, Yahoo, and iCloud Mail rely on DNS records to answer three key questions:
- Is this sender allowed to send mail for this domain?
- Has the message been altered in transit?
- What should happen if something looks suspicious?
DNS problems can affect authentication or routing and increase the risk of delivery issues.
Key DNS Records Used in Email
MX (Mail Exchange) Records
MX records identify the mail servers that receive incoming email for your domain.
Let's follow an incoming message (all names in this example are illustrative, not settings to copy):
- Message addressed to[email protected]
- Look up MX for example.comWhich server receives mail for this domain?MX points tomx.example.com
- Route the incoming messageReceiving mail servermx.example.com
MX identifies the incoming-mail destination
This routes mail to the receiving server, but it does not automatically authorize the servers that send mail for example.com.
If no MX record exists, SMTP can fall back to the destination domain's address records. Keep in mind, that an existing but unusable MX configuration can still prevent delivery.
Again, MX records provide incoming-mail routing, but they do not authenticate outgoing mail.
PTR and Reverse DNS
The sending IP address should have a PTR record pointing to a hostname. That hostname should resolve back to the same IP address through an A or AAAA record.
Let's illustrate the process with an example (these are documentation-only addresses, not settings to copy):
- Start with the sending IP192.0.2.25
- PTR lookup (reverse DNS)Which hostname does this IP point to?PTR hostnamemail.example.com
- A record lookup (forward DNS)Which IP does that hostname point to?Resolved IP192.0.2.25
FCrDNS verified: the IPs match
If the forward lookup returned 192.0.2.99 instead, this check would fail. For IPv6, use an AAAA lookup. This is an illustrative DNS check, not proof that a message is authentic.
If you use an email service provider, confirm this configuration with that provider. Do not assume a change in your domain zone alone will fix the sending IP's reverse DNS.
How HELO/EHLO fits into reverse DNS
When one mail server connects to another, the sending server introduces itself with a command such as EHLO mail.example.com. You would see that command in an SMTP session transcript or a diagnostic log that records SMTP commands, rather than in the email's message body. If you use an email service provider, ask its support team or your administrator to confirm the hostname being announced.
The greeting answers “Which server is connecting?” The visible From address answers “Who is this message from?” A provider's server might announce mail.example.com while sending a customer's message with From: [email protected]. The server hostname identifies the sending infrastructure; the From domain identifies the apparent author of the message. They serve different purposes, so their domain names do not have to match.
The message still needs the appropriate authentication. DMARC checks the visible From domain against a passing SPF envelope-sender identity or DKIM signing domain, rather than requiring it to match the EHLO hostname.
If an email service provider sends for you, ask which hostname its server announces. Our HELO/EHLO hostname guide explains the greeting in more detail.
Here is a simplified SMTP conversation. The server names are illustrative, not settings to copy.
- After the sending server connects220 mx.example.net readyThe receiving server sends its welcome message.
- Sending server → receiving serverWhat does the sending server call itself?The sender introduces itselfEHLO mail.example.com“Hello, I am mail.example.com.”
- Receiving server → sending serverWhich SMTP extensions does the receiver support?The receiver replies to EHLO250 responseThe response lists the supported SMTP extensions.
The sending host has introduced itself
HELO is the original SMTP greeting command. EHLO is its extended counterpart, used with Extended SMTP (ESMTP): it introduces the sender and asks which SMTP extensions the receiver supports. Modern SMTP clients normally try EHLO first and can fall back to HELO if EHLO is not recognized. Neither greeting authenticates the visible From address.
SPF (Sender Policy Framework)
SPF checks whether the connecting IP address is authorized to send an email on behalf of your domain (envelope-sender domain, also called the SMTP MAIL FROM domain). It does not directly validate the visible From address.
If an email comes from an unauthorized source, SPF fails.
Let's illustrate the process with an example how SPF works (these are documentation-only addresses, not settings to copy):
- Connecting sending IP192.0.2.25
- Check the envelope-sender domainEnvelope sender[email protected]
- Read example.com's SPF policy in DNSIs the connecting IP authorized?For this example, the policy authorizes192.0.2.25
SPF passes: the sending IP is authorized
Poor SPF configuration is one of the most common causes of:
- Spam filtering
- Spoofing
- Phishing abuse
DKIM (DomainKeys Identified Mail)
DKIM adds a cryptographic signature to outgoing messages. The sender signs using a private key, and the receiving server retrieves the public key through DNS.
- Sender signs with a private keySigning domain: example.com
- Sender sends the signed messageThe receiver getsMessage + DKIM signature
- The receiver retrieves the public key through DNSCan the receiver verify the signature?The receiver checks the signed message materialPublic key + signature verification
Valid DKIM signature: signed material verified
A valid signature associates the signing domain with the signed message material and helps verify its integrity.
The receiving server checks DNS to verify that:
- The message was really sent by your domain
- The content was not modified
A failed signature can contribute to delivery risk, depending on the receiver's evaluation. But even if an email is delivered - trust drops immediately.
DMARC (Domain-based Message Authentication, Reporting & Conformance)
DMARC connects SPF and DKIM with the visible From domain. DMARC passes when at least one passing SPF or DKIM identity aligns with that From domain.
At least one of these paths must pass and align.
DMARC passes with either aligned path
It tells mailbox providers:
- What to do if authentication fails (
none,quarantine, orreject) - Where to send reports about authentication and abuse
A policy of none, quarantine, or reject describes requested handling, not the authentication result. The receiving provider makes the final delivery decision.
Gmail and Yahoo require bulk senders to use SPF, DKIM, and DMARC, with alignment for DMARC to pass. Both accept p=none.
Publishing a DMARC policy and passing DMARC are separate things. The receiving provider still makes the final delivery decision.
DNS and Sender Reputation
DNS records don’t just authenticate messages; they help build sender reputation.
Consistent DNS alignment allows mailbox providers to:
- Track engagement correctly
- Attribute behavior to the right domain
- Detect abuse faster
Misaligned or broken DNS causes:
- Reputation fragmentation
- Unpredictable inbox placement
- Higher filtering even with good content
How DNS issues can complicate a Spamhaus CSS removal request
Suppose your server has moved, but it still announces the old hostname. If an IP is listed on Spamhaus CSS, its troubleshooting workflow can compare the HELO name it has observed with the IP's PTR record and forward DNS.
Ask your server operator or provider to compare those results with your intended setup. And then correct any identified discrepancy, rerun the checker, and follow the listing's removal instructions.
Keep the scope in mind: that CSS workflow checks matching HELO, PTR, and forward resolution. The broader Spamhaus Sender Guidelines recommend HELO/rDNS name consistency where possible. Keep in mind, that fixing a DNS discrepancy does not guarantee removal or establish why the IP was listed.
Remember, email delivery can still be affected by reputation, recipient feedback, and content. If authentication passes but recipients are complaining, there is more to investigate than DNS.
Common DNS Mistakes That Break Deliverability
- More than one SPF TXT record at the same applicable owner name
- An SPF record evaluation that exceeds the limit of 10 lookup-causing terms, including nested evaluations
- Missing or incorrectly rotated DKIM keys
- Failing to review DMARC reports and assess a suitable policy
- Sending without authentication
A DMARC policy of p=none is a valid monitoring choice, though keeping p=none for good considers a bad practice.
DNS mistakes are invisible to most marketers, but immediately visible to mail servers.
Four Steps to Check Your DNS Setup
- Identify actual sending services and domains with your administrator.
- Check the intended DNS names.
- Send test emails from each real service.
- Inspect receiver results and have discrepancies reviewed.
In Gmail, open More, then Show original. A DNS lookup alone is not an end-to-end test.
Why DNS Is Not “Set and Forget”
DNS changes over time:
- Email providers update requirements
- Infrastructure changes
- New tools and vendors are added
- Domains age and reputation evolves
DNS changes may not be visible everywhere immediately because resolvers cache records according to their TTL. Missing-record answers can also be cached. After changing your DNS configuration, check the published record and run a fresh test.
When rotating DKIM keys, keep the previous public key available for a reasonable validation interval.
DNS must be reviewed regularly, not only when something breaks.
Changed email providers? Review the DNS settings you left behind
Suppose you have retired an email service. Its sending permissions and DNS references need a review too. Ask your administrator to confirm which services are still active before removing records:
- Former-provider SPF includes: is that provider still needed for any outgoing mail?
- CNAME record: does the DNS alias still point to a service you use?
- A or AAAA records: does the hostname still point to an active host? AAAA is the IPv6 counterpart of A.
- NS delegations: ask your DNS administrator whether any unused delegations remain.
This is also a security check. An abandoned provider reference may be abused if someone else can claim the resource it points to. Age alone is not a reason to delete a record. Spamhaus's DNS hygiene guidance covers these retired-service records.
Conclusion
DNS is a foundation of email trust.
You can have perfect content, great offers, and clean lists, but without properly configured DNS, inbox placement will always be at risk.
If email deliverability matters to your business, DNS is not optional.
It’s the first thing mailbox providers check, and one of the hardest things to recover once misconfigured.
Explore EmailConsul
Let EmailConsul help you improve your email deliverability and sender reputation with expert guidance and actionable insights.