Check discovery settings before importing or recreating a zone that is missing from PD BIND 9 DNS. The module discovers matching files in the configured directory; this is separate from the DNS server’s own serving configuration.

Check the connection and pattern

1. Open BIND 9 DNS → Providers and identify the intended server connection.
2. Compare Zone file directory and Zone file pattern with the values supplied by its administrator.
3. Run the connection test and inspect any access or tool error.
4. Open Zones, select the intended provider and check the search/filter choices.
5. Ask the administrator to confirm that the intended files match that directory and naming arrangement.

Discovery is not a recursive search through every server directory. A different filename pattern or a file in a subdirectory can explain why only some zones appear. Do not widen server access or change unrelated provider settings just to list more files.

Separate file discovery from service state

A zone file visible in the module is not proof that the running server serves it. Conversely, a zone can be served through a different layout that the configured discovery pattern does not include. Views, secondary storage and other server arrangements need the responsible administrator’s review.

The released secondary workflow uses a separate transfer arrangement, so do not assume every secondary appears through the ordinary editable-zone file scan. If a known secondary is absent, preserve its creation result and have your hosting team’s BIND administrator check transfer and discovery separately before considering another creation attempt.

Preserve existing DNS

No import is required merely to discover an existing matching editable zone. If records cannot be opened, keep the exact redacted result, intended provider and zone reference. Do not delete files, recreate live DNS or make server repairs from an error message. See the maintenance guide for safe diagnostic checks.

Check zone discovery

Your hosting team’s BIND administrator should compare the intended provider, configured directory/pattern and module search/filter with the actual storage layout and serving arrangement. The ordinary file scan is not a recursive inventory of every view, secondary or server zone. Check an absent secondary’s original declaration and transfer independently; a missing module row does not prove that transfer failed or data was deleted. Do not recreate DNS, widen access or delete files merely to make the zone appear.

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