Check the intended WHM account and zone-discovery results before recreating DNS that looks missing in PD cPanel DNS. Provider visibility, module tracking and public authority are separate facts.

Check account scope first

1. Open cPanel DNS → Providers and identify the correct server and username.
2. Review the connection test and the intended account/token scope.
3. Search Zones with the appropriate provider and filters selected.
4. Ask the server administrator whether the domain is local, account-owned, aliased or hosted through the DNS cluster.
5. Compare the actual domain ownership and current record access.

A reseller’s restricted view may be correct. Do not switch to a server-wide credential simply to conceal an ownership or permission mismatch.

Refresh discovery deliberately

The released zone list combines bulk WHM results with previously discovered account domains. Some account and clustered zones require the background discovery sweep or the module’s available sync action. A list can therefore include retained discovery information rather than a fresh read of every account on every page load.

Use Maintenance and the relevant sync/reconcile action, then inspect its result and Activity. Account-list or cPanel-API restrictions can limit discovery while ordinary listed zones still work. Preserve the original refusal rather than widening every permission.

Investigate listed-but-unavailable zones

If a domain lists but its records cannot open, keep the exact provider, domain, owning-account reference and redacted error. A cached discovery entry is not proof the zone is still available to this connection.

Do not create another zone or delete ownership data as a guessed fix. Ask the administrator to reconcile actual server/cluster state. If records open but public answers differ, check registrar delegation using the zone and delegation guide.

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