Create the intended zone in WHM through PD cPanel DNS, populate its records and then check registrar delegation. Decide whether the domain is DNS-only or will use account-backed forwarding before creation.

Prepare the server and ownership

Confirm the correct provider, existing domain state and intended authoritative nameservers. WHM needs an address for new zone creation; the module can request the server’s shared IP when one is not supplied. The token must be allowed to read the information required by that route as well as create DNS zones.

If the domain has no hosting account and will need forwarding, prepare the fallback-account arrangement first. A DNS-only zone and a domain attached to a cPanel account are not equivalent. Do not delete a working zone to force an account attachment through.

Create and inspect

1. Open cPanel DNS → Zones and the add-zone action.
2. Select the intended provider and enter the zone name.
3. Choose the intended customer owner where appropriate.
4. Create the zone and inspect the returned result.
5. Review SOA/apex nameservers and the actual website, mail and verification records.

When a prepared fallback account is used, the module can attach the domain through that account’s supported route. Domain limits, ownership conflicts and permissions still apply. A failed creation result should be reconciled against actual server state before retrying.

Delegate after the records are ready

Set registrar nameservers to the intended authoritative set, then check public DNS, website, HTTPS and mail separately. Keep previous DNS available through the cache transition where applicable.

Zone creation does not move site files, create mailboxes or complete a domain registration. If WHM refuses an ownership change, retain the exact redacted result and involve the server administrator; do not repair ownership files or recreate unrelated accounts.

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