Bind the intended existing zone to its customer before offering self-service DNS. The module’s client relationship is separate from the native DirectAdmin account that owns the domain.

Assign the intended customer

1. Open DirectAdmin DNS → Zones and identify the exact provider and domain.
2. Open its row actions and choose Assign to client.
3. Select the intended customer and any relevant domain or service.
4. Review the saved binding and the applicable active-service allowance.
5. Confirm that the intended client sees only their own zones.

An unowned zone does not become available to every customer. A module binding does not transfer native domain ownership or grant the provider key access to another DirectAdmin user.

Open the client workflow

Customers use the enabled DNS Manager link or Manage DNS on a linked domain/service. They can manage supported permitted records and download zone data. Keep provider credentials out of this workflow.

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

Diagnose a refusal

Check client ownership, active service and DNS package allowance, zone lock and domain-only policy separately. Protected forwarding records can require changes through the corresponding forward control rather than a direct record delete.

For missing provider domains, use the login-context checks. For a TTL that does not change, use the TTL limitation guide; broadening client permissions does not change that module behaviour.

Keep the original redacted operation result while your hosting team checks the saved binding and policy. Never give a client the DirectAdmin login key or an administrative module token to bypass a portal restriction.

Check customer access

Your hosting team should compare the saved zone/customer binding, related domain/service and applicable active-service allowance with the intended client’s portal. Check lock, domain-only policy and protected forwarding records separately from DirectAdmin login-key permissions. Compare a neutral customer error with the module’s Activity entry at the original time, retaining provider details privately. Do not give a customer a provider key or administrator token to bypass portal restrictions.

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