Map the mail flow before editing DNS

Start by listing every way the domain uses email. Incoming messages may go to individual mailboxes, shared addresses, aliases or a help desk. Outgoing messages may come from staff mailboxes, a website form or a separate notification service. A provider change can affect each path differently: MX records direct incoming mail, while SPF, DKIM and DMARC help receiving systems assess mail sent in the domain’s name.

Record the current DNS values and the new provider’s requested values before changing anything. Note which system hosts the domain’s authoritative DNS; a change made in a control panel that does not serve the live zone will have no effect. Keep account names and recovery details in a secure place rather than putting credentials in a DNS worksheet. The worksheet only needs the relevant record names, types, values and intended purpose.

Prepare the new service while the old one still receives mail

Create the needed mailboxes, aliases and routing rules at the new provider before switching MX records. If the provider offers a way to import existing messages, plan that separately from DNS: changing MX records does not move stored mail. Test access to the new mailboxes using the provider’s instructions, without assuming that a successful sign-in means incoming delivery has already changed.

Prepare outgoing-mail DNS as well. Review the domain’s single SPF record and add the new sender using the mechanism the provider specifies, rather than publishing a second SPF record. Publish any required DKIM records and enable signing in the new service. If the domain has a DMARC policy, check that messages from the new provider can meet its alignment requirements. Keep an old sender authorized only for as long as it still legitimately sends mail; remove obsolete entries after that use ends.

Make the MX change as a controlled cutover

Choose a period when someone can watch both mail systems. If practical, lower the MX record’s time to live ahead of the change, allowing time for the previous value to expire from caches. A shorter TTL can reduce how long some resolvers retain a record, but it cannot force every sender to switch immediately. Set the new MX records exactly as the provider specifies, including their priority numbers, and remove old MX records when the old service should no longer receive new deliveries.

Avoid treating a lower-priority MX record at the old provider as a general-purpose backup. Senders normally try the most preferred available destination, but differing availability and cached answers can leave messages split between systems. An intentional backup MX requires a service configured to accept and relay the domain’s mail correctly. During a routine provider move, it is usually clearer to follow the new provider’s published MX configuration and keep access to the old mailbox during the transition.

Check published records and test both directions

After saving changes, inspect the published DNS records rather than relying only on what the editing form displays. Confirm that the domain’s MX answers name the intended mail hosts and that the SPF and DKIM records are present at the requested names. If results differ between lookups, caching may be involved; also check that the edits were made in the authoritative zone. Do not paste private keys, passwords or full message contents into a troubleshooting request.

Send a test message from an unrelated mailbox to the domain, then reply from the new mailbox. Check where the incoming message arrived and whether the reply was accepted. Repeat with any important aliases or application senders. Message headers can help identify the system that handled a test message and whether authentication passed, but a single successful exchange does not prove every mail path works. Keep watching the old mailbox for deliveries that followed cached MX answers.

Retire the old setup only after checking the overlap

Keep the old service accessible until you have checked for late arrivals, completed any message migration and confirmed that routine senders use the new service. Review website forms, automated notices and devices that may still submit mail through the old provider. Once they have moved, remove DNS records that existed solely for the retired sender, taking care not to delete records shared with another legitimate service.

A short cutover log makes later troubleshooting easier: note what changed, where it changed and which tests passed. It also gives you a starting point if delivery fails and you need to compare the live records with the intended configuration. After the technical work, if you would like a change of pace, browse Table and Dining · Fromadia Home for table-and-dining ideas.

Back to category ↗