Restore the native DirectAdmin domain/account arrangement before trying to recover its DNS records through PD DirectAdmin DNS. A saved record snapshot does not let this module create a standalone zone for an absent domain.

Establish what is missing

Confirm the provider, intended account context and domain. A missing list entry can be a scope problem rather than deletion. Use the visibility guide before taking recovery actions.

If the domain was removed, ask the responsible administrator to review its approved native restoration or service setup. That work can involve hosting and mail as well as DNS. Do not create a duplicate account or delete another domain to satisfy a guessed prerequisite.

Restore the domain, then records

1. Have the administrator confirm the intended native domain exists again under the correct account.
2. Verify that the module’s provider connection can list it and open its records.
3. Review the existing DNS and the saved snapshot’s age and contents.
4. Use the existing-zone recovery workflow for supported ordinary differences.
5. Check the module’s client owner, domain/service binding and allowance afterwards.

The Backups recovery action cannot bypass the module’s standalone-creation restriction. A refusal saying that DirectAdmin creates DNS with the domain is not a reason to repeat the same request.

Verify the wider service

Check authoritative nameservers, registrar delegation, website, HTTPS and mail separately. Account attachments, redirect/email rules, mailbox data and signing private keys are not reconstructed by a BIND record snapshot.

Inspect actual values and TTLs after recovery; individual TTL requests are not applied by this released module. Retain the native restoration result, snapshot reference, original time and redacted module error while your hosting team checks the remaining record differences.

Check the native domain and restored records

Your hosting team should first confirm whether the native domain is genuinely absent, rather than hidden by the connection’s account context or filters. If it is absent, the responsible DirectAdmin administrator must prepare or restore the native domain/account arrangement; repeating the module’s standalone-zone refusal cannot do that. Once the intended domain is visible, compare its current records with the retained snapshot before a deliberate record restore, then check the customer binding and delegation separately.

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