Bind the intended PowerDNS zone to its customer before offering self-service DNS. A provider connection gives the host upstream access; it does not make every zone visible to every client.

Check the binding

1. Open PowerDNS → Zones and find the exact provider and zone.
2. Open the zone row’s actions and choose Assign to client, then optionally one of that customer’s domains or services.
3. Select the intended customer and applicable domain or service.
4. Review the saved owner and any package allowance.
5. Confirm that the customer’s portal lists only the intended zones.

A zone without a recorded client owner does not appear in a client’s DNS area. Check account ownership separately from whether the zone exists at PowerDNS.

Open the customer workflow

Customers use the enabled DNS Manager navigation link or Manage DNS on a linked domain/service. They can manage permitted records, inspect DNSSEC status and download a BIND zone file. Keep staff/provider credentials out of that workflow.

On WHMCS, review the client-navigation and domain/service link choices in PowerDNS → Settings. Check the enabled link and its placement before treating a missing menu entry as a provider failure.

Investigate read-only or missing access

Check the client binding, relevant active service and allowance, zone lock and domain-only policy separately. A locked zone can remain visible while edits are refused. A secondary zone is read-only because its records come from a primary server; unlocking it is not the way to enable local editing.

Confirm the intended account before changing ownership. Do not grant broad provider access or share an administrative API token to work around a customer restriction. Use the allowance guide for entitlement refusals and the secondary guide for transferred records.

Check customer access

Your hosting team should compare the exact provider/zone, intended customer and saved assignment with the optional domain/service relationship, relevant active service, allowance, lock and secondary status. Check the platform’s own portal navigation separately from provider connectivity. Your DNS administrator should review actual records after an uncertain write before the customer repeats it. Do not supply an upstream key or administrative API token to bypass the refusal.

See the PD PowerDNS WHMCS guide for related tasks, or explore PD PowerDNS.