MX records tell other mail systems where to deliver messages for a domain. Use the exact mail-server hostnames and priorities supplied by the chosen email provider, and change them at the domain’s authoritative DNS service.
IN THIS ARTICLE
Check access and requirements
Create and test destination mailboxes before cutover. Export the existing MX set and review SPF, DKIM, DMARC and local email-routing settings. An MX change does not migrate historical messages or automatically configure website SMTP.
01 Add MX records for an email provider in cPanel
- Open Zone Editor > Manage for the domain and inspect its current MX records.
- Add each required MX record with the provider’s destination hostname and priority. Lower numeric priority is preferred when multiple MX destinations exist.
- Enter hostnames rather than IP addresses, URLs or mailbox addresses. Confirm the record applies to the intended domain name.
- Remove obsolete MX entries only as part of the planned cutover. Do not leave an unrelated old provider as a supposed backup unless both services are deliberately configured for that arrangement.
- Configure cPanel Email Routing appropriately for local or remote delivery, then verify public MX answers and send external test messages in both directions.
Confirm the expected result
New mail should reach the intended provider, including messages generated by applications on the hosting server. Check recipient inboxes and actual delivery headers.
Why does local website mail use the wrong destination after an MX change?
If external mail works but local website mail goes elsewhere, review Email Routing. If some senders still use the old destination, account for DNS caching and keep migration access available. Correct authentication records separately; MX records alone do not authorise outgoing mail.