Assign the intended Route 53 zone to its client so the customer can manage DNS through WHMCS. This gives portal access to the zone; it does not give the customer an AWS login or access-key pair.

Review the zone and owner

1. Open AWS Route 53 DNS → Zones and select the intended provider/domain.
2. Check the records and the domain/service that should own this zone.
3. Open the zone menu and choose Assign to client.
4. Select the intended account, and the corresponding domain or service where appropriate.
5. Save, then review the Client and binding information before directing the customer to the portal.

Do not bind a same-named zone from an unrelated AWS account just to make navigation appear. Confirm the domain’s authoritative nameservers separately; a portal link is not proof that this zone serves public queries.

Explain where to open DNS

The customer uses the configured DNS Manager navigation link or Manage DNS on a linked domain/service. Only zones assigned to the account should be visible. The record editor shows the fields relevant to the selected record type, and a zone-file download is available through the supported export workflow.

Record editing and provider-wide administration are different permissions. This client access is not an invitation to let customers create or delete AWS hosted zones through an administrative credential.

Diagnose missing or refused access

Check the account binding, linked domain/service and saved navigation choices before editing records or recreating the zone. A zone lock or domain-only editing policy can restrict available actions. A quota, content rule or provider permission can refuse an individual save even when the customer can view the zone.

A missing signing or forwarding control does not prove a login problem: the module offers controls according to provider support. Route 53 signing is covered separately in the DNSSEC scope guide.

Removing a client binding withdraws portal management without being a request to delete the provider’s hosted zone. Review destructive zone deletion separately, and keep credentials and unrelated client records out of support screenshots.

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.