Use PD AWS Route 53 DNS snapshots to retain a point-in-time record copy before making changes. The released restore workflow imports saved record data; it is not an exact rollback of every Route 53 setting or every change made since the snapshot.

Configure the schedule

1. Open the module’s Settings.
2. Enable Take scheduled zone backups when required.
3. Choose the backup interval and snapshots retained per zone.
4. Review the optional age-based pruning setting.
5. Check the normal Blesta cron and the actual completed snapshots under Backups.

A configured schedule does not prove the latest record change is captured. Count- and age-based retention can prune older snapshots, including manual ones.

Take a current snapshot

Use Back up now for the intended zone or the Backups panel’s all-zones action for the intended wider scope. Inspect the resulting zone name, timestamp and record count, and download the BIND file where useful.

Before a restore, preserve the current record set and identify precisely which previous values are needed. A DNS record snapshot is separate from a website, mailbox or AWS account backup.

Know what this release restores

Restore first needs a successful safety snapshot of the zone as it exists now. It then adds supported records from the saved file through Route 53 import. Values added since the snapshot are not automatically deleted, and a previous address can be added alongside the current one rather than replacing it.

SOA and NS records are skipped by this import. Keep AWS aliases and advanced routing details separately; do not assume a zone-file snapshot fully preserves them. If the current zone is missing and a safety snapshot fails, restore stops. Have your hosting team and AWS administrator establish the missing zone’s identity, delegation and required records before choosing a recovery path; repeatedly recreating it can add more same-named zones.

Verify the intended service

Reload the live records after any recovery and compare the full value sets for important names. Check authoritative DNS, delegation and website/mail operation separately. A completed import is not proof that the domain returned to its previous state.

See the import/export guide for an explicit record import, and keep the snapshot/action time and exact redacted result for support.

Check same-named hosted zones before changes

If your AWS account contains multiple hosted zones with the same domain name, do not assume choosing a same-named row selects a particular hosted-zone ID. This module resolves zones by name. Have your AWS administrator compare the exact hosted-zone ID, records and delegated nameservers before using module writes; use AWS’s native zone-specific controls if the target remains ambiguous. Do not create or delete another zone to diagnose that ambiguity.

Check the recovery result

Your hosting team should compare the snapshot’s provider, domain, timestamp and record count with the intended recovery point. Check the current-zone safety snapshot result first, then the actual imported values. If the zone is missing or its identity is uncertain, have your AWS administrator establish the authoritative hosted-zone ID and required records before choosing a recovery action. Do not repeatedly recreate the zone or treat an additive import as an exact rollback.

See the PD AWS Route 53 DNS Blesta guide for related tasks, or explore the module.