Use PD Google Cloud DNS to manage the intended Google Cloud project’s DNS from WHMCS. A service-account JSON key authenticates the provider connection; it is separate from the PD account used to activate your module licence.

Prepare the project and credential

Install PD Modules, connect the account holding your licence, then install PD Google Cloud DNS from the Store and allow the staff role that needs it. In Google Cloud, identify the intended project ID, rather than its display name or numeric project number.

Enable the Cloud DNS API in that project. Prepare a dedicated service account with the DNS permissions required for the intended zones and records. The module’s setup guide uses DNS Administrator. Google documents both predefined roles and custom permissions in its Cloud DNS access-control guide.

When permitted by your organisation’s policy, create a JSON key for that service account through IAM & Admin → Service accounts → Keys. Keep the downloaded file private: it contains a private key. If key creation is restricted, ask the project administrator for an approved setup rather than bypassing that restriction.

Add the provider

1. Open PD Modules → Google Cloud DNS → Providers → Add a provider.
2. Give the connection a recognisable name.
3. Confirm that the service-account JSON belongs to the intended project.
4. Paste the complete permitted key into Service account JSON.
5. Run Test connection, inspect the result and save the provider.
6. Review a known zone and its records before enabling customer editing.

The module reads the target project from project_id in the saved service-account JSON. Its provider form has a Service account JSON credential field, not a separate project-ID override. Use a provider credential prepared for the intended project; changing a connection label or customer binding does not select another project. Do not edit a downloaded key file to guess a different target.

The connection test lists managed zones. A pass confirms that request, not every record write or optional action. Check that the credential and intended project agree and the service account has access there; add separate labelled provider connections for other projects.

For a refusal, distinguish a disabled API, a sign-in/key problem and missing action permissions. Do not distribute the JSON file to customers or include it in support attachments. See the project and zone-identity guide and key-rotation guide for those tasks.

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