Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Domains & DNS

DNS rollback planning: keep a safe path back during a cutover

Published August 2026 · 2 min read · Updated 2026-09-05

DNS rollback planning is useful only when the previous destination can still serve correct data. A saved old A record is not a recovery plan if the old database is stale, mail was moved, certificates expired, or the previous server has already been terminated.

Preserve the old destination deliberately

Keep the previous service online through the verification window and document its IPs, hostnames, certificates, database state, credentials, and dependencies. If you intend to roll back, know which pieces must also roll back with DNS.

Avoid destructive cleanup immediately after a successful-looking cutover.

Record exact DNS before the change

Save old and new values, TTLs, zone serials, nameserver delegation, and any related records such as MX, CNAME, TXT, or SRV that are part of the same service. Rollback should change the minimum necessary records.

Do not replace an entire zone file to reverse one web record unless the entire zone really changed.

Account for data created after cutover

Orders, accounts, uploads, form entries, messages, and database changes created on the new system will not appear on the old system automatically. Decide whether rollback means a reverse sync, a write freeze, or accepting a defined data-loss window.

This is why stateful migrations need an application plan in addition to DNS.

Test rollback criteria before launch

Write the symptoms that trigger rollback, who makes the decision, how long caches may take to respond, and what verifies recovery. A vague “if anything goes wrong” rule wastes time during an incident.

  • Keep the source usable.
  • Save exact old DNS.
  • Plan reverse data synchronization.
  • Define rollback owner and threshold.

Next step

Prepare old and new endpoints, TTLs, record history and rollback triggers before changing DNS so recovery remains possible if the destination fails.

Explore DotMoose domains and DNS

Keep reading

Related guides.

CAA record planning: control which certificate authorities may issue for a domain

Plan CAA records around the certificate providers you use, subdomains and incident contacts, then verify issuance will still work before enforcing restrictions.

Read the guide

CNAME chain problems: why extra DNS aliases can break or slow resolution

Trace CNAME chains, loops, missing terminal records and provider restrictions, then shorten unnecessary aliases without changing the intended hostname.

Read the guide

DKIM selector rotation: change signing keys without breaking verification

Rotate DKIM selectors by publishing the new key first, switching signers, monitoring authentication and retaining the old selector long enough for queued mail.

Read the guide

More domains & dns guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move