Create a validated editable zone through PD BIND 9 DNS, then have the BIND administrator confirm that the running server serves it. Creating the zone’s record data is separate from server activation and registrar delegation.

Prepare authority and activation

Identify the intended provider and check for an existing zone. Confirm the public Authoritative nameservers in the provider settings. Keep old DNS available during a move and prepare website, mail, verification and any child-zone records.

Ask the server administrator how new editable zones are registered with the running BIND service. The released module can create valid zone data before that operator-managed setup is complete. A successful create result alone is not proof of public availability.

Create and inspect

1. Open BIND 9 DNS → Zones and choose the add-zone action.
2. Select the intended provider and enter the Zone name.
3. Choose the editable Primary — records are managed here option where Zone kind is offered.
4. Set the intended owner or leave the zone host-managed.
5. Create it, inspect its SOA/NS and add the required ordinary records.
6. Have the administrator confirm server activation and the intended authoritative response.

If an edit reports that a change was written but could not be activated, preserve the result. Repeating record writes will not complete missing server activation. Use the diagnostic guide and the responsible administrator’s supported process.

Delegate only after DNS is ready

Update registrar nameservers once this exact zone is served with the required records. Check authoritative answers, then website, HTTPS and mail separately. Retain the previous DNS through the cache transition where applicable.

After a timeout, inspect existing data before retrying creation. Creating DNS hosting does not register the domain, move site files or create mailboxes. Secondary zones have a different transfer workflow.

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