Point a domain or subdomain at the intended IPv4 or IPv6 destination for the website your hosting team or customer is configuring through PD AWS Route 53 DNS. An address-record change updates DNS; it does not configure the website, application or HTTPS certificate on that destination.

Choose the right zone and name

Open AWS Route 53 DNS → Zones, then the intended zone’s records. Customers can use My Tools in the client portal, then the DNS manager. Confirm the domain delegates to this hosted zone’s nameservers before expecting public queries to change.

Keep the intended full hostname and destination address ready. Use A for IPv4 or AAAA for IPv6. A record at the root domain and one at www serve different names; review both if the web host requires both.

Add or edit the address

1. Search for the exact name and type before adding a record.
2. Choose Add record, then A or AAAA.
3. Enter the name, address and appropriate TTL.
4. To replace an existing destination, use Edit on the intended row and compare the old value.
5. Save and reload the zone to check the complete resulting record set.

Several address values at the same name/type can be intentional. Adding a value does not mean the old destination was replaced. Route 53 treats values of the same name and type as a record set with a shared TTL; do not assume each visible row can keep a different TTL.

Verify the visitor result

Check the authoritative response, then a normal resolver and the intended website. DNS caches can retain the earlier destination until its prior TTL expires. If the public DNS answer is correct but the website or certificate is wrong, review hosting and HTTPS configuration separately.

Do not add a CNAME at a name already used for these address records. Use the CNAME and alias guide when the destination is a hostname rather than an IP address. For a refused change, inspect the actual policy, lock, quota or AWS permission error before retrying.

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.

Check the saved address set

Your hosting team and DNS administrator should compare the full name, A/AAAA type, complete saved record set, shared TTL and authoritative answer with the intended website destination. Adding another address does not replace an older one, and a successful DNS answer does not configure the application or certificate. Review the exact lock, quota, content-policy or AWS refusal before editing again. Do not remove intentional multiple destinations to diagnose one connection.

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