Incorrect MX records can send mail to the wrong server or prevent delivery entirely. This is especially common after a website migration or nameserver change.
Common symptoms
- Inbound mail bounces immediately
- Mail is delivered to an old provider instead of cPanel mail
- Webmail works locally but outside senders get failures
Troubleshooting steps
- Review the domain's current MX records in the authoritative DNS zone.
- Confirm whether your email is hosted on the cPanel server or with a third-party provider such as Microsoft 365 or Google Workspace.
- Remove outdated MX entries that point to previous providers.
- Verify any required companion records such as SPF and autodiscover records match your mail provider.
- After making changes, allow DNS propagation and retest from an external sender.
Additional notes
- Website DNS and email DNS can be managed in different places; confirm the active authority before editing.
- A valid MX record is not enough if the mail server itself is not intended to receive mail for the domain.
When to contact support
Contact support if the domain should receive mail locally but the server continues rejecting recipients.