Quick answer
An MX record points to a mail-server hostname, not an IP address. Keep the authoritative MX set and the hosting account's local/remote mail routing consistent.
Applies to
For an authorized reseller or administrator whose Interactive Online service includes the relevant WHM permission. Ordinary website hosting uses cPanel and does not imply WHM or root access. Work only with accounts you own or are explicitly authorized to administer. The video is an older interface reference.
Steps
- Obtain the actual mail provider's complete MX records and preserve the existing zone.
- Open the domain's permitted MX/DNS editor and enter the required hostnames and priorities. Lower numbers have higher preference.
- Confirm Local or Remote mail routing for that account according to where mail is hosted. Review related authentication records separately.
Check the result
Check authoritative MX answers and controlled incoming/outgoing delivery. An unrelated secondary MX is not a harmless backup.
Troubleshooting and support
If the domain uses external DNS, update that provider's zone. Send support the redacted error and old/new records if delivery fails.
If the problem continues, contact support from the account that owns the service. Include the domain, exact error, time and time zone, tool name, and a redacted screenshot. Keep passwords, private keys, cookies and private message content out of the ticket.
Video tutorial
The original video is preserved. Its interface or product version may differ from the written guidance above.
Related help
Official references
Written content reviewed November 1, 2026. Menu availability depends on the product version, permissions and service.
