Assign the intended zone to its customer before offering self-service DNS. The module’s client binding is separate from the cPanel account that owns the domain at WHM.

Assign and check the customer

1. Open cPanel DNS → Zones and identify the provider and zone.
2. Open its row actions and choose Assign to client.
3. Select the intended customer and any relevant domain/service relationship.
4. Review the saved binding and applicable active-service allowance.
5. Confirm the intended client’s DNS page lists only their own zones.

An unowned zone does not become visible to every client. Changing the module’s owner does not itself move the domain between cPanel accounts or grant new WHM token permissions.

Open self-service DNS

Clients use the enabled DNS Manager navigation link or Manage DNS on a linked domain/service. The supported workflow offers permitted record edits and zone-file downloads; DNSSEC also depends on the server backend and access policy.

On WHMCS, review the DNS navigation and domain/service link settings in the module.

Diagnose missing or read-only access

Check account ownership, the relevant active service and DNS package allowance, zone lock and domain-only policy separately. A visible locked zone may be intentionally read-only. Forwarding-managed records can be protected from ordinary edits.

For a refused signing operation, check the DNSSEC prerequisites rather than changing the customer binding. For missing provider data use the discovery checks. Never give clients the WHM token or an administrative module API token to work around portal restrictions.

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