Keep a known record snapshot before changing an existing DirectAdmin domain’s DNS. PD DirectAdmin DNS supports scheduled and on-demand BIND-format snapshots; verify the saved result rather than assuming a configured schedule produced a usable recovery point.

Take and review a snapshot

1. Open DirectAdmin DNS → Zones and identify the intended domain and provider context.
2. Use the available on-demand backup action.
3. Open Backups and check the snapshot’s domain, time and result.
4. Inspect or download its available data where required.
5. Keep its reference before editing live records.

For Back up all zones now, inspect the result and use an offered continuation if the time budget did not cover the whole list. Check reported failures in Activity rather than assuming every zone was included.

Check scheduled work

Review schedule and retention settings and confirm the normal Blesta cron. Inspect an actual recent snapshot and the relevant Maintenance result. A passing connection test is not proof that every domain was backed up.

Understand what can be recovered

Snapshots preserve record data, not the complete DirectAdmin domain, hosting files, mailboxes, forwarding rules or secret signing keys. The module cannot recreate an absent standalone zone; restore the native domain/account arrangement through the responsible administrator first.

Use the existing-zone record recovery guide for supported value differences and the removed-domain guide when the domain is absent. Requested record TTLs are not applied by this released write path, so confirm actual TTL policy separately. Keep older snapshots until the intended recovery point has been checked.

See the PD DirectAdmin DNS Blesta guide for related tasks, or explore the module.