Use a PD cPanel DNS snapshot to restore supported ordinary records towards an earlier state. This can remove later values and change TTLs; review the intended recovery point before applying it to live DNS.

Identify the snapshot and dependencies

Confirm the provider, exact zone and snapshot time. Compare website, mail, verification and forwarding changes made since then. Keep the responsible WHM administrator available if account ownership or provider restrictions are involved.

Restore and inspect

1. Open cPanel DNS → Backups and choose the intended snapshot.
2. Review its target and use the restore action deliberately.
3. Confirm that the existing-zone safety snapshot succeeds.
4. Inspect additions, removals, TTL changes and any skipped or failed work.
5. Read back current records and verify affected public services.

The released restore requires a successful safety snapshot for an existing zone. It compares saved and live records, removes extra supported ordinary values, adds missing ones and adjusts relevant TTLs. Provider SOA/apex NS, protected forwarding-managed records and unsupported live data are preserved as applicable.

The restore is a sequence of changes and can stop part-way. A safety snapshot is an available recovery point, not a promise of automatic rollback or one indivisible server transaction.

Handle a partial result

Keep both snapshot references, action time and exact redacted result. Inspect what now exists before repeating the restore or selecting another recovery point. If the safety snapshot fails, investigate that refusal rather than trying to bypass it.

Ordinary record recovery does not reconstruct cPanel ownership, forwarding configuration, signing private keys or registrar delegation. Use the missing-zone guide when the provider zone itself is absent.

See the PD cPanel DNS WHMCS guide for related tasks, or explore the module.