Use Maintenance and Activity to separate account visibility, provider refusal and record-result problems. DirectAdmin DNS management depends on the intended native domain already being available to the selected login context.

Inspect the original result

1. Identify the provider, domain and intended DirectAdmin account context.
2. Review current records and the exact action in Activity.
3. Open Maintenance and inspect the relevant task’s last result and time.
4. Confirm the normal Blesta cron for scheduled tasks.
5. Run only the relevant available maintenance action and read its result.

The connection test lists the login’s own domains. The released zone lookup does not populate authoritative nameservers, so a health warning about missing nameservers needs separate authority checks; it is not proof a working zone is broken.

Diagnose record outcomes precisely

An edit adds a replacement before removing the old value; a removal refusal can leave both values. Read the whole affected record set. A successful-looking write is not proof that a requested individual TTL changed, because the released module does not send it.

For import or recovery errors, inspect actual state before repeating a write. A safety snapshot gives a recovery point, not automatic rollback. An absent domain must be restored through its native account arrangement before module record recovery can work.

Keep deletion and access separate

The module does not delete standalone zones; provider cleanup/termination requests can therefore report a refusal while native DNS remains. Removing a module binding is different from removing the domain in DirectAdmin, which can affect hosting and mail.

Do not broaden a restricted key or remove a live domain to hide a warning. Keep the account/domain reference, requested action, original time and redacted result while your hosting team checks the affected task. Never send login keys, private signing keys or unrelated user data.

Check the maintenance result

Your hosting team should identify the original task, provider/zone, last-run time and relevant Activity result. Compare read-only connection/discovery/health observations separately from current DNS, customer binding and public service behaviour. Inspect partial import/restore/cleanup state and retain recovery references before retrying a write. Use your own DirectAdmin administrator for native account ownership, domain preparation or signing configuration.

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