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 BIND 9 DNS server and can perform the required zone operation. The connection test checks directory and required tool access; it does not prove every zone write or server activation.

In this BIND-only module, automatic new zones use the oldest eligible BIND provider that is enabled and accepts new domains. A provider set to existing domains only is not a destination for new setups. Review those saved provider choices and intended nameservers before enabling automation; this is separate from a cross-provider routing control.

Enable and inspect

1. Open BIND 9 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 WHMCS, documented triggers include domain registration/transfer and new services with a relevant domain. Confirm the resulting client and domain/service relationship, not only the original order result.

Automatic creation does not move a website or mail service. Where you deliberately enable nameserver takeover for selected TLDs, the module can request a registrar nameserver change once its prerequisites are met. On WHMCS, the registrar integration must accept the nameserver change. Inspect Activity and the registrar result, then verify public delegation separately. If that route is unavailable or refused, use the domain’s supported registrar process after your BIND administrator confirms the zone is actually served.

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.

Confirm server activation

New editable zone data can be created before the running BIND server is configured to serve it. Have the administrator complete that preparation and verify authoritative answers. A successful lifecycle action or zone-file creation does not prove activation; do not offer automatic public DNS until this part is ready.

Check the created zone and delegation

Your hosting team should compare the original platform event, usable domain name, eligible provider, allowance and existing zone/binding with Activity and any queued setup result. Your BIND administrator should inspect actual zone data and server activation before a retry; zone creation and billing success do not establish that DNS is served or the registrar accepted a nameserver change. Review any selected-TLD takeover result separately from ordinary service setup.

See the PD BIND 9 DNS WHMCS guide for related tasks, or explore the module.