Use a retained PD cPanel DNS snapshot to recover a genuinely missing provider zone. First distinguish deletion from a missing client binding, limited token scope or incomplete discovery.

Review the recovery prerequisites

Identify the correct server, zone and suitable snapshot. Have the administrator confirm account ownership and whether the domain is attached to a hosting or fallback account. Creation may need the server’s shared IP and the permissions for that route.

If WHM still reports ownership or attachment conflicts, stop and preserve the exact result. Deleting a DNS zone does not necessarily clear every account/domain relationship; do not edit server ownership data or repeatedly recreate the zone as a guessed repair.

Recover and inspect

1. Open cPanel DNS → Backups and select the missing zone’s intended snapshot.
2. Review the target and use the available recovery action.
3. Inspect zone creation and supported-record restoration results.
4. Read back the actual records and provider SOA/nameservers.
5. Verify the client owner and any domain/service binding before offering access again.

The released recovery can recreate an absent zone and restore supported ordinary data. Do not assume that restoring record data reconstructs the customer owner or former domain/service relationships. Verify the saved module binding and assign the intended client if needed before offering access again. A genuinely absent zone has no current-zone safety snapshot.

Check the complete service

Review public delegation, website and mail separately. Account attachments, redirects, email forwarding and signing private keys are not reconstructed simply by restoring a BIND file. Unsupported record types can be skipped and provider refusals can leave partial recovery.

Keep the snapshot reference, original action time and redacted result while your team checks an incomplete recovery. See the existing-zone restore guide for the different safety-snapshot procedure.

Check the recovered zone

Your hosting team should first confirm whether the provider zone is genuinely absent, rather than hidden by token scope, discovery or a missing client binding. Compare the intended provider/domain, retained snapshot, WHM account/fallback ownership and actual zone/record state after the original attempt. If a creation or restore partly succeeded, inspect it before repeating recovery. Verify the module’s customer binding and public delegation separately; do not assume they were reconstructed from record data. Use your own WHM administrator for ownership or account restrictions.

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