Website DNS Changes: A Migration Checklist

DNS changes must match the services actually handling your website and email. Before a migration, record the existing configuration and obtain the destination provider’s verified settings. Old Business Catalyst server instructions should not be reused.

Record What Each Service Uses

Before changing anything, make an inventory of the domain’s website, email and verification records. Identify the authoritative DNS provider and confirm who can make changes. A nameserver switch can affect the whole zone, not just the website. Preserve a copy of the current configuration.

Separate The Website From Email

Changing the destination of a website does not necessarily require moving mailboxes. Review the records used for mail delivery and authentication with the email provider. Keep verification records needed by other services. Avoid removing a record merely because its purpose is unfamiliar.

Prepare And Test The Destination

Configure the destination website and certificate before the public change. Test the intended domain names, redirects, forms and static assets. Coordinate any caching or time-to-live adjustments with the provider and allow for differences between resolvers. Do not promise an instantaneous worldwide switch.

Change Deliberately And Verify

Apply only the agreed records, record the time and check the public website and email journeys. Keep the previous service available for the agreed overlap period. If something fails, compare against the saved configuration and use the rollback plan. DNS work is easiest to recover when each change has a clear purpose and owner.