Email DNS Records Explained

Email authentication requires specific DNS records to ensure proper delivery and security. Here's how to set up the essential records for your domain:

MX Records (Mail Exchange)

• Direct email to the correct mail server
• Multiple records possible with different priorities (0-255)
• Lower priority numbers indicate preferred servers
• Format: @ IN MX [priority] [mail server]

Pre-configured MX records available for:

• Google Workspace
• Microsoft 365
• Fastmail
• Proton Mail
• Neo
• Titan
• iCloud
• Zoho Mail

Authentication Records

DKIM (DomainKeys Identified Mail):

• Verifies email authenticity
• Added as TXT or CNAME record
• Format: [selector]._domainkey IN TXT [DKIM value]

SPF (Sender Policy Framework):

• Specifies authorized email senders
• Added as TXT record
• Begins with "v=spf1"
• Multiple records automatically merge

DMARC (Domain-based Message Authentication):

• Enforces email authentication policies
• Added as TXT record at _dmarc.[domain]
• Helps prevent email spoofing
• Only one record allowed per domain

SRV Records (Service Records): Required components:

• Service name (e.g., _smtp)
• Protocol (e.g., _tcp)
• Priority (optional)
• Weight (1-5)
• Port number
• Target hostname

Best Practices:

1. Keep records updated
2. Verify syntax carefully
3. Allow time for propagation
4. Monitor authentication results
5. Regular maintenance checks

Each record type serves a specific purpose in email authentication and delivery. Proper configuration helps ensure emails reach their destination and protects against spoofing and spam.

Related Articles

Previous Articles