Review the connection’s owning-account context before creating or restoring DNS that appears missing in PD DirectAdmin DNS. This module lists the domains belonging to the effective login context.

Check the intended account

1. Open DirectAdmin DNS → Providers and identify the server and username/context.
2. Run the connection test and inspect any authentication or command refusal.
3. Confirm with the administrator which account actually owns the domain.
4. Search Zones with the correct provider and filters selected.
5. Review a known domain’s records to check the intended scope.

An administrator or reseller can have domains outside their own user-domain list. The released module does not perform a server-wide account sweep merely because the login has an administrator role. An approved owning-user or impersonation context may be needed; have the server administrator prepare it.

Separate visibility from absence

A domain missing from this list may still exist on another account. Changing its client binding inside the module does not move native ownership or expand the login key’s privileges.

Do not create another hosting domain or restore records over a working account just to make a list match. First establish whether the intended domain exists and is available to the selected context.

Investigate a genuinely absent domain

The module does not create standalone DNS zones for absent domains. DirectAdmin creates DNS with its domain, so the native domain/account arrangement must be restored or prepared through the responsible administrator before module management can resume.

Keep the intended provider, domain/account reference, original time and redacted result while your hosting team checks the actual login context. Use the existing-domain management guide or domain-removal recovery guide for the appropriate next step. Never send login keys or unrelated user-domain exports.

Check the visible domains

Your hosting team should compare the provider’s effective login context and domain list with actual native account ownership. Confirm the selected provider and filters, known-domain read result and original authentication/command refusal with your DirectAdmin administrator. A missing entry can mean a different account scope, not deletion. Do not create another domain, restore over a working account or broaden customer access merely to make the list match.

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