Enable automatic zone creation only after the provider, ordinary records and client-ownership policy are ready. A completed billing lifecycle action is separate from successful DNS hosting and public delegation.

Prepare the intended provider

Confirm that the connection reaches the correct cPanel DNS server and can perform the required zone operation. The connection test lists zones; it does not prove every create, account attachment or signing action.

In this WHM-focused module, new setups need an enabled cPanel/WHM connection that accepts new domains. A provider marked for existing domains only is not the intended target for new zones. Review which eligible connection will be used, along with its authoritative nameservers, before enabling automation; do not assume any connected provider is eligible.

Enable and inspect

1. Open cPanel DNS → Settings.
2. Review Automatically create a DNS zone on registration and new services.
3. Enable it for the intended service policy.
4. Follow a controlled normal activation process.
5. Inspect Zones and Activity for creation, records and the correct owner/binding.

On Blesta, review the relevant domain/service activation and resulting client binding through its normal lifecycle. Use the actual platform result rather than relying on registrar hook names from another billing system.

Automatic creation does not move a website or mail service and is not proof that registrar nameservers changed. Verify delegation through the appropriate registrar process once the zone is ready.

Plan termination and cleanup

Review Keep the DNS zone when a service is terminated, Automatically clean up orphaned zones and When cleaning an orphan, also delete the zone at the provider before cancellation or cleanup. Removing a management relationship and deleting live provider DNS have different effects.

Keep an appropriate snapshot and retention policy for zones still serving traffic. After an uncertain create result, check what actually exists before repeating it. Preserve the lifecycle event, action time and redacted error if the DNS action failed.

Review nameserver takeover separately

On Blesta, nameserver takeover can request the change through the Domains plugin’s registrar layer when that route is available and the registrar accepts it. Match the intended TLD takeover list, confirm that the zone and authoritative nameservers are ready, and inspect the separate takeover result in Activity. If the route is unavailable or the registrar refuses the change, complete delegation through its supported workflow. The takeover list does not filter which domains can receive zones. Confirm account/fallback prerequisites before enabling the lifecycle policy.

Check the created zone and delegation

Your hosting team should compare the lifecycle event, automation setting and provider eligible for new setups with the actual WHM zone, current records and module customer/domain/service binding. A saved connection or completed order does not establish that DNS creation or registrar nameserver update succeeded. Check Activity for creation and takeover outcomes separately, then verify actual delegation. Inspect an uncertain creation before repeating it.

See the PD cPanel DNS Blesta guide for related tasks, or explore the module.