← Back to Guides

DNS backup and recovery checklist

Use this checklist for domains and DNS services you own or are authorised to manage. Start with one zone. Record what you can prove, what needs checking and who owns the next action. Do not test recovery by overwriting production records.

Last updated 4 Nov 2026 · maintained by Myles Agnew

Progress is saved in your browser only — nothing is sent anywhere. Use Pass / Needs work / Needs checking / Not applicable for each item.

Scope and ownership

1. Identify the domains/zones in scope and confirm authority to manage them.

Evidence: a non-sensitive inventory reference and named owner.

2. Record who controls the registrar, authoritative DNS and hosting accounts.

Evidence: access owners and an approved escalation path, not passwords.

3. Identify web, mail, verification and third-party service dependencies before a change.

Evidence: a dependency checklist without secret values.

Backup coverage and storage

4. Verify that the backup includes the expected record types and zones.

Evidence: timestamp, zone count and representative record checks; do not assume a successful job covered every record.

5. Record what the chosen format omits, such as account settings or provider-specific metadata.

Evidence: tested coverage notes against the provider/tool documentation.

6. Keep dated copies outside the source DNS account with access restricted to authorised operators.

Evidence: storage location reference and access owner; never publish private exports in a public repository.

7. Check scheduled-run failures and confirm the newest usable backup matches your change cadence.

Evidence: last successful run plus archive presence, kept separate from recovery proof.

Recovery preparation

8. Document how approved operators would retrieve a backup if the primary account were unavailable.

Evidence: a tested access path; keep MFA recovery materials in the approved secret store, not this checklist.

9. Review registrar delegation, DNSSEC, proxy behaviour and TTL assumptions separately.

Evidence: provider-specific recovery notes; do not disable DNSSEC or lower TTLs across production just to complete a checklist.

10. Define change approval, verification and rollback before a live recovery.

Evidence: named approver, affected services and a plan to validate mail/web/service records.

Test and evidence

11. Rehearse representative recovery in a dedicated test zone or other isolated environment.

Evidence: test scope, observed outcome and gaps. Do not overwrite production to demonstrate readiness.

12. Record whether only the export was inspected or a real recovery rehearsal succeeded.

Evidence: timestamp, who checked it, remaining risks and next review trigger after material changes.

What this checklist does not guarantee

A readable export, a successful scheduled job and a successful recovery test are different evidence levels. None guarantees every future recovery will succeed. Provider settings, access and service dependencies can change.

Subscribe for updates

Get new security tools, checklists and guides by email. No spam — unsubscribe anytime.

Please don't include passwords, secrets, or client data.