DNS Migration Checklist
Plan a DNS migration with a practical checklist for TTL, delegation, old and new records, propagation checks, and one-shot alerts.
Plan the DNS move before the cutover
A DNS migration checklist keeps the quiet details from turning into downtime: lowering TTL early, confirming the authoritative provider, recording the old value, publishing the new value, and checking public resolvers after the change.
Use the checklist for website moves, mail migrations, CDN launches, and DNS-provider changes. It links directly into the WhereIsDNS health check, delegation check, propagation checker, and change tracker so each step produces evidence instead of guesswork.
What to check before changing DNS
- Current records: capture the existing A, AAAA, CNAME, MX, TXT, and NS answers before editing.
- TTL: lower the TTL one old-TTL window before a planned cutover so caches expire quickly later.
- Delegation: confirm the registrar points to the DNS provider you are actually editing.
- Rollback value: keep the previous record handy in case the new target fails.
After the DNS change
Compare the old value with the new one across public resolvers. If some resolvers still show old and others show new, you are seeing normal cache propagation. If every resolver still shows old, the change probably was not published where the internet is looking. If an unexpected value appears, pause and inspect the authoritative zone before declaring the migration complete.
FAQ
When should I lower TTL?
Lower TTL at least one old-TTL window before the migration. If the current TTL is 24 hours, lower it a day before the cutover, not minutes before it.
What record types should I check for a website move?
Check A and AAAA records for direct IP moves, and CNAME records when the hostname points at a platform or CDN. A stale AAAA record can affect IPv6 users even when A records look correct.
What record types should I check for an email move?
Check MX records first, then verify SPF, DKIM, and DMARC TXT records. MX controls inbound delivery, while SPF, DKIM, and DMARC affect whether outbound mail is trusted.
How do I know propagation is finished?
Run the DNS Change Tracker with the old and new values. Propagation is finished when every resolver returns the new value and no resolver returns old, mixed, missing, failed, or unexpected answers.
Can I get notified instead of refreshing?
Yes. From the tracker, create a one-shot propagation alert. It sends a confirmation email first, then notifies you when all resolvers return the new value or an unexpected value appears.