Skip to main content

Roll back a DNS record change

Restore a previous record configuration, verify authoritative answers, and confirm that the affected service has recovered.

Before you begin

  1. Confirm that your assigned roles permit you to update or create records.

  2. Identify the affected zone and record.

  3. Obtain the previous record configuration from your saved change details or a snapshot.

  4. Confirm that the previous destination or service remains available.

  5. Coordinate the rollback with anyone making related changes.

For a secondary zone, restore the record at the primary provider and verify that the corrected data transfers to DigiCert®​​ DNS.

Identify the failed change

  1. Go to DNS > Zones > Primary zones and open the affected zone.

  2. Open Records and locate the changed record, if it still exists.

  3. Compare its current name, type, values, and TTL with the intended configuration.

  4. Check the applicable regional view if regional views are enabled.

  5. Review DNS audit logs to identify the relevant activity and timing.

  6. Identify any later changes that must be preserved.

Before restoring the record, confirm that the earlier configuration is still the appropriate recovery target.

Retrieve the previous configuration

  1. Locate the record values saved before the change.

  2. Confirm the previous name, type, values, TTL, and regional configuration.

  3. If using a snapshot as your reference, open Snapshots.

  4. Check the snapshot’s date, name, and description to identify the version created before the failed change.

  5. Select Download JSON to obtain its saved data.

  6. Review the downloaded data for the previous record configuration.

Downloading a snapshot does not change the zone.

Restore the previous record

Reverse a record update

  1. On Records, open the affected record’s edit action.

  2. Confirm that you are editing the intended record and regional view.

  3. Replace the current values with the saved previous values.

  4. Review TTL and set the value required for recovery.

  5. If TXT validation is available, validate the restored content.

  6. Select Update.

  7. Review the saved record.

Recreate a deleted record

  1. Select Add record.

  2. Choose the previous record type.

  3. Enter the saved name, values, and TTL.

  4. Restore the appropriate regional configuration, if applicable.

  5. Review any additional options before saving. For A or AAAA records, check Configure reverse PTR to avoid unintentionally creating reverse records.

  6. Select Save and close.

  7. Confirm that the recreated record matches the saved configuration.

Review any related PTR records separately. Forward-record changes do not automatically reverse changes to PTR records.

Restore a snapshot when broader recovery is needed

Use this procedure only when you intend to restore the zone’s saved state, including its settings and records.

  1. Review changes made since the snapshot was created and identify anything that would be replaced.

  2. If you need to preserve the current state, create a new snapshot and wait for it to finish.

  3. On Snapshots, locate the recovery snapshot.

  4. Select its Restore icon.

  5. Review the snapshot name and all warnings in the confirmation dialog.

  6. Select Restore.

  7. Review the restored zone settings and records.

Restoring a snapshot replaces the current zone state with the saved state. When Regional Views configuration differs, the restoration also replaces that configuration and its records.

For a single-record rollback, restore the record manually when unrelated changes need to remain in place. See DNS snapshots for restoration details.

Verify authoritative responses

  1. Obtain the assigned nameserver hostnames from the zone’s Nameservers tab.

  2. Use a DNS lookup tool to query the restored record’s full name and type directly against each assigned authoritative nameserver.

  3. Compare each answer with the intended recovery values.

  4. If answers differ, review the saved record and applicable regional configuration.

  5. Open Health and investigate any relevant nameserver or synchronization issues.

If external secondary providers also serve the zone, verify that they have received the restored data.

Account for cached responses

  1. Query the restored record through your usual recursive resolver.

  2. Repeat the query through another resolver.

  3. Compare the responses with the authoritative answers.

  4. If a resolver still returns the failed value, allow for the TTL associated with that cached answer to expire.

  5. If you recreated a deleted record and a resolver still reports it as missing, allow for its cached negative response to expire.

  6. Repeat the checks until the tested resolvers return the expected result.

A rollback does not immediately replace answers already held in resolver caches.

Confirm recovery and document the rollback

  1. Test the affected website, email service, application, or verification process.

  2. Confirm recovery with the service owner.

  3. If you temporarily changed the TTL, restore the intended operating TTL after recovery is confirmed.

  4. Review the rollback activity in DNS audit logs.

  5. Record the affected records, original change time, rollback time, restored values, and verification results.

  6. Document any remaining issues or follow-up work.

Next steps