Use PD PowerDNS to bring an existing PowerDNS Authoritative server’s zones and records into Blesta. The upstream PowerDNS API credential is separate from the PD account used to activate the module.

Prepare protected API access

Install PD Modules, connect the account holding your licence, then install PD PowerDNS from its Store. Allow the staff role that needs the module. Ask the administrator responsible for PowerDNS to prepare API access that your billing server can reach through suitable protected transport and network restrictions.

The ordinary PowerDNS API key gives broad server API access; it is not a credential limited to one customer’s zone. Keep it private. The PowerDNS API documentation describes the upstream access model.

Add and test the provider

1. Open PD Modules → PowerDNS → Providers and add a PowerDNS connection.
2. Give it a recognisable name.
3. Enter the base API URL, including its port where required. Do not append the API version path; the module adds that.
4. Enter the supplied API key and Server ID.
5. Run Test connection, inspect its result and save.
6. Review a known zone and its records before enabling customer access.

The connection test reads the server endpoint. It does not prove that every zone write, transfer or signing action works. The Server ID is the upstream API identifier, not necessarily the server’s public hostname.

Investigate a refusal

Check the exact base URL, server identifier and current key with the server administrator. A timeout can indicate reachability or network restrictions rather than a bad key. Do not expose the API to everyone to make a test pass, or send the credential in a support attachment. Use the rotation guide when replacing a key.

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