Coordinate a PowerDNS API-key change with the server administrator and every integration using that server. Updating the upstream key does not update the connection saved in PD PowerDNS.

Identify the affected connections

Open PowerDNS → Providers and identify the intended API URL and Server ID. Check which other billing installations, monitoring systems or tools use the same upstream API credential.

The ordinary upstream server uses a configured static API key. Do not assume it supports separate simultaneous keys for each caller, a per-zone permission scope or an automatic overlap period. A module automation token is a different credential and does not replace this server key.

Coordinate the replacement

1. Agree the change with the PowerDNS administrator and the owners of affected integrations.
2. Have the administrator replace the upstream credential through their supported server-management process.
3. Edit the matching provider connection in PD PowerDNS.
4. Replace its saved API key, leaving the intended URL and Server ID intact.
5. Run Test connection, save and review known zone records.
6. Confirm the other affected integrations have also been updated.

Where changing the server invalidates the previous key immediately, plan for the resulting interruption rather than promising a seamless overlap. Server administration is separate from the module’s provider form.

Verify the right failure

A successful connection test proves the server read used by that test. Check a refused record or signing action separately. Keep the exact redacted result and action time if the replacement fails; do not repeatedly rotate keys to fix a wrong URL, unreachable server or unsupported backend operation. See the connection guide for those checks.

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