Prepare the domain on DirectAdmin, then connect and bind its existing DNS zone in PD DirectAdmin DNS. The module does not create a standalone DNS zone for a domain that is absent from the selected account context.

Prepare the native domain

Have the responsible administrator confirm the domain exists under the intended DirectAdmin account and that the provider connection can see it. Domain creation or restoration is a separate native account operation; it can affect hosting and mail, so use the intended service plan.

Check the current zone and authoritative nameservers before a move. Keep previous DNS available while records and delegation are prepared.

Link and inspect management

1. Open DirectAdmin DNS → Providers and test the intended connection.
2. Open Zones, select that provider and find the existing domain.
3. Inspect its current website, mail, verification and authority records.
4. Use Assign to client where the zone should belong to a customer.
5. Review the relevant domain/service binding and DNS allowance.
6. Confirm the intended client’s own DNS view.

If the add-zone action reports that DirectAdmin cannot create a standalone zone, inspect the account/domain prerequisite rather than repeating the create. Changing the module’s owner does not change DirectAdmin account ownership.

Verify public authority separately

Once the intended records are ready, confirm registrar delegation points to the nameservers actually serving the zone. Check authoritative answers, website, HTTPS and mail separately and allow for previous cached answers.

Automatic lifecycle management follows the same existing-domain prerequisite. Use the automatic binding guide for that policy, or the visibility guide if the native domain exists but is missing from the module.

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