A secondary zone receives its records from a primary nameserver. PD BIND 9 DNS can request that server-side transfer arrangement, while ordinary edits belong at the primary rather than the secondary.

Prepare the server arrangement first

Ask the BIND administrator to prepare the module’s secondary-zone integration and the primary server’s transfer permissions. Obtain the primary server IP addresses and, where required, the name of an already-configured TSIG key. The form does not create or distribute the TSIG secret for you.

Secondary storage and discovery differ from the ordinary editable-zone file arrangement. Have the administrator confirm how transferred zones will be served and reviewed before offering one to a customer.

Review the available creation controls

1. Open the add-zone form under BIND 9 DNS → Zones.
2. Choose the intended provider and zone.
3. Select Secondary — transferred from a master (read-only).
4. Enter Master nameserver IP(s) and the prepared TSIG key name (optional) where applicable.
5. Inspect the creation result and have the administrator confirm actual transfer and service state.

Creation, completed transfer and module visibility are separate checks. The released ordinary zone scan uses the configured editable-zone directory/pattern; it does not establish that every transferred secondary is discoverable there.

Avoid duplicate creation or local repairs

If the secondary is missing from the list or its records cannot be opened, retain the original result and have your hosting team’s BIND administrator check the actual transfer, storage and discovery arrangement. Do not recreate the zone repeatedly, move transferred files or change server configuration from a guessed repair.

Make record changes at the primary and confirm they reach the secondary. Public authority still depends on the intended delegation and server response. Do not treat a missing secondary view as evidence that the transfer itself failed, or use import/restore to turn it into an editable zone.

Check the secondary transfer

Your hosting team’s BIND administrator should compare the intended zone, prepared primary-server addresses and TSIG key name with the original secondary creation result and actual server transfer state. Check server integration and transfer permission separately from the module’s ordinary editable-zone discovery. A failure can follow a saved secondary declaration; review the existing declaration and transfer before another attempt. Do not move transferred files or use import/restore to bypass secondary read-only controls.

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