Some links on this page are affiliate links. We may earn a commission when you click through and make a purchase, at no additional cost to you.
Understanding MX records is crucial during Kinsta migrations, as these records ensure uninterrupted email service. Many site operators mistakenly believe that web hosting and email services are tightly linked, but they function independently, allowing for seamless transitions.
When migrating to Kinsta, it’s vital to grasp how your MX records interact with your web hosting setup. The Domain Name System (DNS) manages records separately, ensuring that email servers remain stable during hosting transitions. This separation means that while A records change to point to the new server, MX records stay intact, continuously routing emails to the correct servers.
Scenario 1: Email Hosted Separately
In most cases, email services like Google Workspace or Microsoft 365 operate on separate infrastructures from web hosting. This arrangement allows the migration of a website to Kinsta without affecting email operations. As Kinsta recommends, keeping email services separate from web hosting isolates potential disruptions, ensuring smooth transitions.
Scenario 2: Email and Website on the Same Server
Some hosting services bundle email with web hosting, complicating migrations. Kinsta doesn’t provide email hosting, which is optimal for maintaining dedicated email infrastructure. When migrating from a bundled service, it’s advisable to switch to a third-party email provider before site migration to avoid service interruptions.
Scenario 3: Changing Both Providers
Switching both web and email providers simultaneously requires meticulous planning. Running parallel email systems during testing ensures a seamless transition. Configure new MX records in your DNS management alongside existing ones, initially with lower priority, and test thoroughly before making them live.
What To Do
- For separate email hosting: No changes needed to MX records when migrating sites.
- If email and website are together: Transition email to a dedicated provider before migration.
- Changing both providers: Run parallel systems and test before switching DNS records.
