How to Add an MX Record in cPanel

What MX Records Do (30-Second Recap)

An MX record tells senders which mail server accepts email for your domain. Lower priority numbers are tried first, and the destination must be a hostname — an IP address is not valid in an MX record. The whole edit takes five minutes in the Zone Editor:

1. Open Zone Editor — cPanel > Domains > Zone Editor, pick your domain
2. Filter MX — click MX (or + MX Record) to see existing mail routing
3. Add the record — host '@', priority (10/20/30 for backup servers), destination (mail host, e.g. ASPMX.L.GOOGLE.com)
4. Set TTL — 3600 is fine; lower it before planned migrations
5. Save and verify — dig MX yourdomain.com or a checker tool after propagation

Mail routing should match reality: Local mail exchanger when mail lives on this server, Remote when a service like Google or Zoho handles it. The business email hosting plans pair with our business email setup guide for the full MX/SPF/DKIM sequence.

Step 1: Open Zone Editor in cPanel

Log in to cPanel and open Domains > Zone Editor, then find your domain's row in the list. One rule decides whether this step works: DNS records take effect only where the domain's nameservers point. If Cloudflare or your registrar manages the zone, add the MX record there instead — the cPanel zone is ignored, and an edit made in the wrong place changes nothing.

Step 2: Add the MX Record (Host, Priority, Destination)

Click + MX Record on your domain's row. When switching providers, delete the existing default MX first — usually mail.yourdomain.tld — so the old and new sets do not compete. Then fill in the dialog: Priority, where the lower number wins (0 is the highest); Destination, the mail hostname such as ASPMX.L.GOOGLE.COM — an IP address is rejected because an MX destination must be a name; and TTL, where the default 3600 is fine.

Example: Google Workspace MX Values

New Google Workspace setups use a single record: smtp.google.com at priority 1. Existing (legacy) domains instead run five records:

• ASPMX.L.GOOGLE.COM — priority 1
• ALT1.ASPMX.L.GOOGLE.COM — priority 5
• ALT2.ASPMX.L.GOOGLE.COM — priority 5
• ALT3.ASPMX.L.GOOGLE.COM — priority 10
• ALT4.ASPMX.L.GOOGLE.COM — priority 10

Remove every non-Google MX record first, and copy the exact values your Google Admin console shows — the console is the authority for your domain.

Example: Zoho Mail MX Values

Zoho's standard set is three records: mx.zoho.com (priority 10), mx2.zoho.com (priority 20) and mx3.zoho.com (priority 50). Add all three, remove the default mail.yourdomain.tld MX, then finish SPF and DKIM in the Zoho control panel — the TXT record setup guide covers those values.

Mail Routing Settings: Local vs Remote Exchanger

Open cPanel > Email > Email Routing and make the setting match where mail actually lives: Local Mail Exchanger when this server accepts the domain's mail, Remote Mail Exchanger when Google, Zoho, Microsoft 365 or another provider does. The default "Automatically Detect Configuration" reads only the local zone and never re-checks after DNS changes — set the routing manually whenever you change MX records.

Verify and Troubleshoot MX Propagation

TTL is how long a resolver may cache a DNS answer. After an edit, people who cached the old record keep it until that timer ends, so the change can look instant for you and old everywhere else. Drop the TTL a day before a migration, make the change, and raise the TTL once you have confirmed the new target.