Back up and restore DNS records

A DNS backup records the zone's entries so you can review or restore a previous configuration. Use it before imports, bulk changes, nameserver moves or a new mail setup. It is separate from backups of website files, databases and email messages.

01 Create and check a backup

  1. Open the intended domain and select Backups.
  2. Create a backup using the action offered for your package.
  3. Wait for the backup task to complete, then check its date, domain and record contents.
  4. Download a copy when that action is available.

The account-wide Backups view can group snapshots for several zones into one run. Check which zones actually completed. A queued run has not yet secured every record simply because it appears in the list.

02 Restore a previous configuration

  1. Record or export the current DNS configuration first, even if it is partly wrong. It may contain valid changes made after the older backup.
  2. Select the backup for the exact domain and time you need.
  3. Preview the restore. Compare additions, replacements and removals against the current zone.
  4. Preserve any later valid changes, such as a new mail provider or verification TXT record, in your recovery plan.
  5. Confirm the restore and follow the DNS change until provider application and verification complete.
  6. Check the public DNS answers and the affected website or email service.

03 Understand the limits

Restoring records does not renew a domain, replace registrar nameservers, recreate deleted mailboxes or restore a provider's signing keys. If delegation points somewhere else, restored records here may still not answer public queries. If DNSSEC or provider ownership changed, ask support to review that configuration as part of recovery.

Your package determines whether backups are allowed and how many are retained. Older snapshots may be removed according to retention. Keep an independent export before a major migration if you may need it beyond the included history.

Why was my DNS backup restore refused?

Read the displayed reason. A zone lock, changed ownership, unsupported record type, ended allowance or a current change can prevent restoration. Resolve that condition before retrying. Do not delete and recreate the domain to force a restore. Send support the domain, backup date and operation reference so the correct snapshot can be investigated.

  • 0 Users Found This Useful
  • domains-dns, domain-nexus
Was this answer helpful?

Related Articles

Use bulk DNS changes across one or several zones

Bulk management is useful when several records need the same new address or TTL. It also...

Add a domain registered elsewhere to your DNS Manager

You can manage DNS for a domain registered with another company when your Nabtech service...

Read a DMARC aggregate report in DNS Manager

The Premium DNS Plus report reader helps you inspect a DMARC aggregate report received from an...

Enable DNSSEC and complete the DS-record setup

DNSSEC lets validating resolvers check signed DNS data against a chain of trust. It needs both...

Create a website redirect with Domain Forwarders

Domain forwarding sends a visitor from your domain to another web address. An ordinary redirect...