How to Setup Domain DNS Records for Zoho Mail Integration

Setting up Zoho Mail DNS records requires adding specific MX, TXT, and CNAME records to your domain's DNS zone to verify ownership and enable email delivery. Without these exact records, your custom domain cannot send or receive messages through Zoho's servers. Follow this guide to configure your domain correctly the first time.

Before you start making changes to your live domain, it is best practice to verify your current configuration using the DNS Lookup tool to check existing records and ensure there are no conflicting entries that could break your mail flow.

Essential Zoho Mail DNS Records Explained

To integrate Zoho Mail fully, you need to configure four main types of DNS records. Each record serves a distinct purpose in routing mail, proving your domain ownership, and protecting your brand from spoofing.

1. MX Records (Mail Exchange)

MX records tell sending mail servers where to deliver incoming emails for your domain. Zoho provides a primary and a secondary MX record with specific priority numbers.

• Host/Name: @ (or leave blank for root domain)

• Record Type: MX

• Priority: 10

• Value/Points to: mx.zoho.com

• Host/Name: @

• Record Type: MX

• Priority: 20

• Value/Points to: mx2.zoho.com

(Note: If your provider requires a trailing dot, use mx.zoho.com. and mx.zoho2.com. depending on your regional datacenter.)

2. TXT Record for Domain Verification

Before Zoho allows you to receive mail, you must prove you own the domain by adding a unique alphanumeric string provided in your Zoho Mail admin console.

• Host/Name: @ (or your domain name)
• Record Type: TXT
• Value/Points to: zoho-verification=zb12345678.zmverify.zoho.com

3. SPF Record (Sender Policy Framework)

SPF prevents spammers from sending unauthorized emails on behalf of your domain. You must publish a single SPF record that includes Zoho's servers.

• Host/Name: @
• Record Type: TXT
• Value/Points to: v=spf1 include:zoho.com ~all

Important: If you already have an SPF record for another service (like Google Workspace or a newsletter tool), you must combine them into a single record rather than creating two separate ones, such as v=spf1 include:spf.protection.outlook.com include:zoho.com ~all.

4. DKIM Record (DomainKeys Identified Mail)

DKIM adds a cryptographic digital signature to your outgoing emails, assuring receiving servers that the message actually originated from your domain and was not altered in transit.

• Host/Name: zoho._domainkey (or the selector provided by Zoho)
• Record Type: TXT
• Value/Points to: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQ... (Long string provided by Zoho)

5. CNAME Record for Webmail (Optional)

If you want users to access webmail via a custom URL like mail.example.com, add a CNAME record.

• Host/Name: mail
• Record Type: CNAME
• Value/Points to: zm.zoho.eu (or zm.zoho.com depending on region)

Step-by-Step Configuration Guide

Log in to your domain registrar or DNS hosting provider (such as Cloudflare, GoDaddy, Namecheap, or Route53). Navigate to your domain management dashboard, find the DNS management or Zone Editor section, and follow these steps.

Step 1: Add the Verification Record

1. In your DNS manager, click Add Record.
2. Select TXT as the record type.
3. Enter @ or your root domain in the Name field.
4. Paste the verification string zoho-verification=... into the Value field.
5. Save the record and return to the Zoho Admin console to click Verify.

Step 2: Configure MX Records

1. Delete any existing MX records pointing to old email providers to prevent mail delivery conflicts.
2. Add the primary MX record with priority 10 and value mx.zoho.com.
3. Add the secondary MX record with priority 20 and value mx2.zoho.com.
4. Save both records.

Step 3: Add SPF and DKIM Records

1. Create or update your TXT record for SPF using v=spf1 include:zoho.com ~all.
2. Copy the DKIM selector name (usually zoho) and the public key provided in your Zoho Mail control panel.
3. Create a new TXT record where the host name is zoho._domainkey and the value is the long RSA public key block.

Verifying Your DNS Setup

Once you have added all records, you need to verify them. DNS changes can take anywhere from 5 minutes to 24 hours to propagate globally, though most modern DNS hosts update within a few minutes.

Use command-line utilities to check your records directly:

# Check MX records
nslookup -type=MX example.com

# Check SPF TXT records
nslookup -type=TXT example.com

# Check DKIM records
dig +short TXT zoho._domainkey.example.com

You can also use PowerShell on Windows:

Resolve-DnsName -Name example.com -Type MX
Resolve-DnsName -Name example.com -Type TXT

Comparison of Zoho Mail Regions and Hostnames

Zoho operates multiple datacenters globally. Ensure you use the correct hostnames corresponding to your account registration region.

Common Mistakes and How to Fix Them

Even experienced engineers occasionally make mistakes when configuring mail DNS. Watch out for these frequent issues:

• Multiple SPF Records: Having two separate v=spf1 records causes authentication failures. Combine them into a single record.
• Trailing Dots in Hostnames: Some DNS providers automatically append your domain name to host fields. If you enter zoho._domainkey.example.com, it might mistakenly become zoho._domainkey.example.com.example.com. Check your provider's convention.
• Incorrect MX Priorities: Assigning a priority of 1 to both records or reversing them can cause mail delivery timeouts. Always use 10 and 20.
• Leaving Old MX Records Active: Forgetting to delete legacy Google Workspace or Microsoft 365 MX records splits your mail delivery and causes missing emails.

Quick Checklist for Zoho Mail DNS Setup

• Removed conflicting legacy MX records
• Added TXT domain verification record and verified in Zoho
• Configured MX primary (mx.zoho.com, priority 10)
• Configured MX secondary (mx2.zoho.com, priority 20)
• Published SPF record (v=spf1 include:zoho.com ~all)
• Added DKIM TXT record (zoho._domainkey)
• Tested propagation using lookup tools