Innovate | Connect | Transform
ContactService statusUSD $

GICT knowledge base

Point cPanel MX Records to an Intended Local Mail Service

Published

WHMcPanel

To receive a domain’s mail on a cPanel server, configure both the public MX destination and the server’s local mail-routing role. These are separate settings. Changing an MX record does not copy old messages, create mailboxes or make a server ready to accept a domain automatically.

Prepare local delivery before cutover

Confirm the domain and mailboxes exist on the intended server, storage and service limits are suitable, and the mail-server hostname is supplied by the administrator. Preserve the existing MX set and required old mail. If moving from Google Workspace or another provider, plan data preservation and the overlap period before removing its receiving records.

Publish a hostname, not an IP

At the authoritative DNS provider, create or update the domain’s MX entry to the approved mail hostname with its preference. That hostname needs appropriate A/AAAA records and should not itself be a CNAME. The old instruction to point the MX directly to the server IP was incorrect.

cPanel account users can use Domains > Zone Editor > Manage when authorized. WHM administrators use the current DNS Zone Manager. If public DNS is external, make the change there instead of assuming a local zone edit publishes it.

Set the local routing role separately

In cPanel > Email > Email Routing, select the exact domain and the intended Local Mail Exchanger role, or the administrator-approved configuration. Automatic detection uses the local zone and is not a live check of every external DNS change. Do not choose Backup or leave a remote role merely because it appeared in an old configuration.

Use the Email Routing guide for mode boundaries. Do not indiscriminately mix providers’ MX records as a substitute for a documented split-delivery or secondary-exchanger design.

Verify before retiring the old service

Query the actual authoritative MX answer and the target’s address records, then compare a recursive resolver. Test authorized mail from outside and from an application on this hosting server, since wrong local routing can affect those paths differently. Inspect errors, quotas and actual destination folders. Preserve the prior configuration for rollback; do not repeatedly delete mailboxes or wait a fixed day when authoritative answers are already wrong.

References: cPanel Zone Editor and Email Routing.

Reviewed October 15, 2026. Documentation review only; no domain MX, local routing, mailbox or customer migration was performed.

Related guides

Account services are unavailable until the production backend is configured.