Search and AI Visibility Updated
How do you handle DNS changes during a website migration?
The short answer
Lower your DNS record time to live a day or two before launch, record every existing DNS record, change only the records the website needs, and keep email records untouched. Then confirm the new site, SSL, and email all work.
Key points
- Save a copy of all current DNS records.
- Lower the time to live before the switch.
- Change only website records, such as A and CNAME.
- Leave email records like MX, SPF, DKIM, and DMARC alone.
- Confirm SSL and both www and non www addresses work.
Step by step
- 01Export or screenshot every DNS record.
- 02Lower the time to live on the records you will change.
- 03Point the website records to the new host.
- 04Confirm the SSL certificate is issued.
- 05Redirect the non preferred hostname to the preferred one.
- 06Test email sending and receiving.
- 07Raise the time to live again once stable.
Common mistakes
- Deleting email records and losing email.
- Forgetting verification records for Google or other tools.
- Leaving both www and non www versions live without a redirect.
From our team
How Proven ROI helps
Proven ROI coordinates DNS changes during website launches, including redirects, SSL, and checks that email and verification records stay in place.
Talk to a real personCommon follow up questions
- How long do DNS changes take?
- Many changes appear within minutes or hours, but resolver caches and nameserver changes can take longer. Monitor the old and new hosts rather than assuming every visitor has switched.