PD AWS Route 53 DNS can create a hosted zone from billing-platform lifecycle events. Review the account, client ownership and delegation plan before enabling it: creation at AWS and making that zone authoritative are separate actions.

Prepare the provider

Connect the intended AWS account and verify permissions for zone creation as well as listing and records. A successful Test connection only proves the tested listing request. Review the default provider, whether it is accepting new zones and whether an existing hosted zone already serves the domain. A default set to existing domains only can send new setups to another eligible provider; confirm the actual selection in Activity.

Keep the intended initial records ready. Creating an empty hosted zone does not transfer the website, mail or verification records from an old DNS service.

Enable the lifecycle setting

1. Open AWS Route 53 DNS → Settings.
2. Review Automatically create a DNS zone on registration and new services.
3. Enable it for the intended lifecycle policy.
4. Follow a controlled normal registration/activation process and inspect Zones and Activity for the result.
5. Confirm client assignment and records before handing over editing access.

On Blesta, the documented platform flow creates zones when the relevant domain or domain-bearing service is activated. Verify the resulting zone and account binding rather than assuming an event name from another billing system.

Treat takeover and delegation separately

Automatic TLD nameserver takeover is not available on Blesta. Arrange the registrar delegation through the appropriate registrar process after the intended hosted zone and records are ready.

A newly created hosted zone can have a different assigned nameserver set from an older same-named zone. Verify the exact zone and its NS records before changing a registrar delegation. A background failure does not mean the customer’s main registration/service action was rolled back.

Review cleanup before cancellation

Check Automatically clean up orphaned zones and When cleaning an orphan, also delete the zone at the provider before ending services. Removing management access and deleting live AWS DNS are different outcomes.

Keep a current snapshot and a deliberate retention decision for DNS that still serves traffic. For a failed or uncertain create, reconcile existing zones before trying again; retain the domain, action time and redacted result for support.

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 created zone and delegation

Your hosting team should establish which lifecycle action ran and which configured provider accepted new zones. Inspect Activity and compare AWS creation, customer assignment and registrar delegation as separate results. A successful registration or service activation does not prove that the DNS setup completed, and a DNS failure does not mean that the billing action was undone. Check existing hosted-zone IDs before repeating creation and saved retention/deletion choices before cancellation.

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