Identify the authoritative provider and the precise records you intend to change. Export the zone where supported and separately record provider-specific settings such as proxy status, flattening, routing policy, delegation and DNSSEC state.

1. Record each affected owner name, type, complete value set, TTL and relevant priority or service fields. Include record identifiers when your DNS manager uses them for exact updates.
2. Write the intended replacement and the conditions that will trigger rollback. For website moves, verify the old and new servers can coexist without losing new orders, uploads or mailbox data.
3. Lower relevant TTLs in advance when appropriate, then allow the previous TTL to expire before relying on the shorter lifetime. Do not claim the new TTL immediately changes existing caches.
4. Apply one planned group of changes and retain its audit/job identifiers. Verify authoritative publication before judging public resolver results.
5. If rollback is necessary, restore the exact prior record sets and provider settings. Keep both service destinations working until stale answers have aged out and application data is reconciled.

Check authoritative answers, independent resolvers and real website/email workflows in both change and rollback directions. Record the time at which each observation was made.

A whole-zone restore can erase unrelated changes made after the backup. Prefer an exact reversal of the affected records when available. DNSSEC keys, registrar DS and nameserver host objects may require coordinated recovery outside the zone editor.

• Choose DNS TTL values for a planned service migration
• Keep a portable DNS inventory when the provider has no export button
• Move a signed domain to another DNS provider without a stale DS record
• Move a branded nameserver to a new IP without breaking its customer zones

• RFC 1034
• Cloudflare: DNS record export