Domains, DNS & Business Email

A migration may appear complete while aliases, shared mailboxes, mobile clients, forwarding, or DNS authentication remain configured on the old service. Checks to make Inventory all addresses and mail flows, validate inbound and outbound delivery, check SPF, DKIM, and DMARC, test shared resources and client setup, and reconcile mailbox counts. Retain...

A registrar transfer and a DNS hosting change are separate operations; combining them without planning can disrupt services. Checks to make Document current nameservers and records, confirm access to the authoritative DNS account, identify website and email dependencies, and verify transfer locks and contact email. Keep DNS authority stable during...

Email gateways may reject certain file types or containers even when the message size is within limits. Checks to make Capture the non-sensitive rejection notice, compare delivery with a permitted test file, and check sender and recipient policies. Use an approved secure file-sharing method for blocked content rather than renaming a file to bypass...

Changing nameservers can remove the active MX and authentication records if the new DNS zone is incomplete. Checks to make Confirm current delegation and restore the required mail records at the active authority, including MX and applicable SPF, DKIM, and DMARC. Verify external answers and controlled inbound and outbound delivery, then monitor while...

A domain move can leave SPF, DKIM, or DMARC records at the former DNS provider or point them to obsolete senders. Checks to make Confirm authoritative DNS, inventory all approved sending sources, publish the correct records at the active authority, and verify selectors and alignment using controlled messages. Remove old entries only after confirming no...

Forwarding rules can be overlooked during migration and may continue delivering mail to inactive or unauthorized destinations. Checks to make Inventory mailbox aliases and forwarders, confirm business purpose and recipient access, and recreate approved routes at the new service. Test delivery and authentication, then remove obsolete forwarding only...

MX or authentication records can remain at a former mail host after migration, causing split delivery or authentication failures. Checks to make Confirm authoritative nameservers and current MX, SPF, DKIM, and DMARC records. Compare them with the active provider’s documented values and check for legacy hosts still sending. Change records carefully and...

Forwarders that point between mailboxes or domains can create repeated delivery attempts and delayed queues. Checks to make Trace the envelope recipients and forwarding rules across both services, identify the cycle, and remove the unintended link. Test with a controlled message and inspect queue behavior before clearing held mail. When to get help...