Replace the login-key value saved in PD DirectAdmin DNS while preserving the intended server and account context. Creating a new key at DirectAdmin does not change the module’s provider automatically.

Review the current scope

Open DirectAdmin DNS → Providers and identify the server and username. Check the old key’s permitted commands, source addresses, expiry and use limit, along with any other integration sharing it.

Prepare a replacement login key through the intended account’s Login Keys page. Keep the same approved scope unless the responsible administrator has identified a specific additional operation. The key name is a label; the key value is the credential used with the username.

Replace and verify

1. Edit the matching provider in PD DirectAdmin DNS.
2. Replace its login key field with the complete new value.
3. Run Test connection and save.
4. Read a known domain and its records in the intended account context.
5. Check any refused optional action separately.
6. Retire the old key only after replacement and shared uses are confirmed.

The test reads a domain list. A passing result does not establish DNS-control or forwarding permission for every domain. Do not rotate repeatedly to fix an account-scope or certificate problem.

Keep credentials private

Login keys and module automation tokens serve different purposes; rotating one does not rotate the other. Keep either value out of screenshots, client notes and tickets.

If the replacement fails, preserve the exact redacted result and action time. Check the intended username, key restrictions and secure endpoint using the connection guide.

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