Use Maintenance and Activity to identify the failed operation before changing tokens, recreating zones or removing records. A connection test, zone-health indicator and public website check establish different things.

Inspect the original result

1. Identify the WHM provider and exact zone under cPanel DNS → Zones.
2. Review the current records, client binding and relevant action in Activity.
3. Open Maintenance and check the task’s last result and time.
4. Confirm the normal Blesta cron for scheduled discovery, health and backups.
5. Use the relevant sync or health action deliberately and inspect its result.

The provider connection test lists zones. The zone-health probe reads the provider zone and reported nameservers; neither is a website, mail-delivery or full DNSSEC validation test.

Separate permission and discovery problems

A reseller’s limited zone view can be expected. Account/cluster discovery may require additional approved account access and a completed background sweep. A listed domain whose records cannot open needs its exact ownership and provider result checked, not another copy of its zone.

For creation, distinguish missing shared-IP access, account limits and domain ownership conflicts. Forwarding needs a suitable account arrangement. Do not replace every restricted token with unrestricted access or delete ownership data to hide the original refusal.

Reconcile partial or destructive work

Import, restore and cleanup can report partial outcomes. Inspect actual current records before repeating a write. Keep recovery snapshots and exact redacted results.

Review termination retention and orphan/provider deletion choices before cleanup. Explicit Delete zone is destructive provider work; removing a client binding is different. If a domain is attached to a fallback account, removing its final forwarding arrangement can affect that attachment too. Use the forward-removal guide before acting on it.

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