DNS Cutover Guide
A practical sequence for moving DNS with clear checkpoints and a rollback path.
Golden ruleThe destination zone must be complete before nameservers change. Missing mail records can interrupt email even when the website works.
1
24–48 HOURS BEFORE
Prepare
- Complete the DNS backup guide.
- List the website, email, VPN, authentication, and third-party services in use.
- Prepare exact replacement records and have a second person review them.
- Lower TTL where appropriate so future changes are noticed sooner; never change TTL blindly.
2
BEFORE THE WINDOW
Set the go / no-go checks
- Choose a low-traffic change window and notify affected people.
- Confirm access to both old and new DNS providers.
- Record baseline checks for website, email sending and receiving, and key services.
- Define who can approve rollback and keep the old configuration available.
3
DURING THE WINDOW
Make the smallest change
- Apply only the reviewed records; avoid unrelated cleanup.
- If changing nameservers, confirm the destination zone is complete before switching.
- Record the exact change time and keep a change log.
- Do not repeatedly edit records while caches are still updating.
4
AFTER THE CHANGE
Verify
- Test the root domain and www address from more than one network.
- Send and receive external email; check MX, SPF, DKIM, and DMARC where applicable.
- Test important subdomains, logins, payment links, and third-party services.
- Continue monitoring through the previous TTL period.
5
IF A CRITICAL CHECK FAILS
Roll back
- Stop making new changes and capture the failure.
- Restore the saved records or previous nameservers exactly.
- Re-run the baseline checks and document the outcome.
- Escalate to SaaSTech support with the domain, change time, backup, and observed error.
Do not start the cutover unless all are true
✓ Complete, dated backup
✓ New records reviewed
✓ Access to both providers
✓ Rollback owner available