Identify the correct zone, customer and backend. Capture a recent export or backup and check whether another operation is pending. For a live website or mail migration, prepare replacement services before removing the old records.

1. Build the changes through the supported record editor, import or bulk workflow.
2. Open the preview and review additions, updates and removals. Compare complete owner names, record types, values, TTLs and priorities.
3. Check protected records, provider-managed entries, limits and type conflicts. A validation failure should be corrected in the proposed change, not bypassed with an unrelated administrator tool.
4. Choose immediate application or a supported scheduled time. If approval is required, make sure the reviewer sees the exact proposed change.
5. Submit once and retain the resulting changeset or job reference.

Queued or accepted means the request has been recorded. It does not prove the provider has completed every change. Follow the job and read the final result, then verify the records on the provider and authoritative nameservers.

When more than one server participates, inspect each target. A complete master update can coexist with a failed target. Public resolvers may also continue returning an older answer until its cache expires.

If the provider connection fails after a write was sent, the module may not know whether it landed. Use Lost answers and Check the server now. Reconcile the observed result before marking it done or attempting another run. The recovery workflow rereads the server to prevent treating an unapplied change as complete or blindly duplicating an applied one.

Do not create a second unrelated change simply to clear a pending status. That can obscure the original outcome or overwrite a later legitimate edit.

Restoring a snapshot or applying an undo is a new validated DNS change. Preview it against today's records and protect additions made after the original change. A DNS changeset does not restore website files, a database, registrar ownership or DNSSEC signing keys.

• Resolve DNS drift and changes with an unknown provider outcome
• Configure DNS backups and restore a reviewed record snapshot
• Synchronize a DNS package across multiple servers and select its master
• Use bulk DNS changes across one or several zones