Create a public hosted zone through PD AWS Route 53 DNS, then delegate the domain to that specific zone. A hosted zone appearing in the module does not by itself make Route 53 authoritative for the domain.

Check for an existing zone first

Open AWS Route 53 DNS → Zones and search for the domain. Confirm the selected provider/account. AWS permits several hosted zones with the same name; each can have a different nameserver set. Repeated creation is not a fix for editing the wrong copy.

This guide concerns public DNS hosting. Do not use it as a procedure for a private VPC hosted zone or for registering a domain. A domain registration and its DNS hosting can be managed separately.

Create and populate the intended zone

1. Choose Create zone and enter the domain you intend to host.
2. Review the provider/account before confirming.
3. Check the returned result and the new zone’s record list.
4. Add or import the website, mail, verification and other records the domain needs.
5. Review its client assignment before granting portal access.

AWS creates the zone’s own apex NS and SOA records. Keep those provider-assigned records intact. Read the assigned nameservers from the zone’s NS record or the matching Route 53 hosted-zone details; do not copy nameservers from a different hosted zone with the same name.

Delegate and verify

Update the domain’s nameservers through its registrar to the intended zone’s assigned nameservers. The registrar action is separate from adding ordinary DNS records. AWS’s public hosted-zone considerations explains why the exact delegation set matters.

Keep the previous DNS service available through the resolver transition where applicable. Check authoritative answers and important website/mail services before considering the cutover complete. A cache may still show older answers after the new zone is ready.

If the domain was signed at its previous DNS host, plan the signing/DS transition with the DNSSEC scope guide. For an uncertain create response, reconcile the existing zones before trying again; AWS hosted zones can incur provider charges.

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.