Use a PD Plesk DNS snapshot to recover supported ordinary record values in a domain that already exists and is visible to the provider connection. This can remove later values, so review the intended recovery point first.

Confirm the domain and snapshot

Identify the correct server, Plesk account scope, domain and snapshot time. Compare website, mail, verification and forwarding changes made since that point. Resolve visibility problems before deciding that the domain has been deleted.

Restore and inspect

1. Open Plesk DNS → Backups and select the intended snapshot.
2. Review its target and use the restore action deliberately.
3. Confirm the existing-zone safety snapshot succeeds.
4. Inspect additions, removals, skips and any reported failure.
5. Read back the actual records and check authoritative DNS and affected services.

The shared restore requires a current safety snapshot for an existing zone, then compares saved and live ordinary data. It preserves provider SOA/apex NS, protected managed records and unsupported live data as applicable. Provider operations are sequential and can stop part-way.

Check values and TTLs separately

Plesk edits add the replacement before removing the old value. A refused old-value removal can leave both values present, so inspect the complete affected record set even after a successful-looking edit.

This released module does not send requested individual TTLs. Do not treat the recovery result as proof of an exact earlier TTL; use the TTL checks. The safety snapshot provides another recovery point, not automatic rollback.

Keep both snapshot references, action time and exact redacted result for support. If the domain itself is absent, the module cannot recreate its standalone DNS zone; use the native domain-restoration procedure first.

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