Replace the WHM API token saved in PD cPanel DNS without changing the intended server or customer bindings. Creating a token in WHM does not update the module’s provider automatically.

Review the current connection

Open cPanel DNS → Providers and identify its WHM hostname, username and intended features. Check the original token’s expiry, allowed source addresses and whether another integration uses it.

Create a replacement through WHM → Development → Manage API Tokens, using the privileges approved for the same tasks. Keep a working token available during verification where appropriate; do not revoke unrelated tokens just because their names look similar.

Replace and verify

1. Edit the matching provider in PD cPanel DNS.
2. Replace its WHM API token with the complete new value.
3. Run Test connection and save.
4. Review the intended zones and records.
5. Check any previously refused optional operation separately.
6. Revoke the obsolete token only after the replacement and its other uses are understood.

The connection test lists zones; it does not establish permission for every DNS write, account lookup or forwarding action. A wrong source-address restriction, expiry and missing privilege need different corrections.

Keep the credentials distinct

The WHM token authenticates the server connection. A module automation token is a separate integration credential; rotating one does not rotate the other. Neither belongs in a ticket, customer note or screenshot.

If replacement fails, retain the exact redacted result and action time. Check the secure endpoint and intended account before generating more tokens. Use the connection guide for the broader setup checks.

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