Connect PD AWS Route 53 DNS to the AWS account holding your hosted zones. The module manages your DNS through that connection; customers use their billing portal rather than receiving your AWS credentials.

Prepare the account and permissions

Install PD Modules, connect the account holding your licence, then install PD AWS Route 53 DNS from the Store and allow the staff role that needs it. Keep the PD licence connection separate from the AWS provider connection.

Prepare a dedicated AWS identity and its Access Key ID and Secret Access Key for this integration. Do not use root-account credentials. Store the secret privately and keep it out of screenshots, client notes and support attachments.

The workflow uses ListHostedZones, ListHostedZonesByName, GetHostedZone, ListResourceRecordSets and ChangeResourceRecordSets. Creating or deleting hosted zones additionally needs the corresponding CreateHostedZone or DeleteHostedZone permission. Use AWS’s Route 53 action/resource reference when scoping these actions to your intended resources; do not assume every list action accepts the same resource restriction as a record write.

Add the provider

1. Open PD Modules → AWS Route 53 DNS → Providers.
2. Choose the AWS Route 53 provider form.
3. Enter a recognisable label and the prepared access-key pair.
4. Run Test connection and inspect the result.
5. Save the provider, then review its zones and an intended record set before relying on it.

The connection test lists hosted zones. A successful test does not prove record changes or optional lifecycle actions are authorised. Route 53 DNS is global; changing a region setting will not reveal zones owned by another AWS account.

Diagnose and rotate deliberately

For an access refusal, identify the exact AWS action and resource before changing permissions. For a network error, check the billing server’s outbound API access. If a zone is missing, confirm the account and zone identity rather than creating a duplicate.

Create replacement credentials, update the provider, test and save, then revoke the old key once the replacement is confirmed. See the hosted-zone and delegation guide before enabling automatic creation.

Check same-named hosted zones before changes

If your AWS account contains multiple hosted zones with the same domain name, do not assume choosing a same-named row selects a particular hosted-zone ID. This module resolves zones by name. Have your AWS administrator compare the exact hosted-zone ID, records and delegated nameservers before using module writes; use AWS’s native zone-specific controls if the target remains ambiguous. Do not create or delete another zone to diagnose that ambiguity.

See the PD AWS Route 53 DNS WHMCS guide for related tasks, or explore the module.