DirectAdmin
Manage DNS-01 records through a DirectAdmin server via its API (username + password or login key).
Prerequisites
- A DirectAdmin login that manages the DNS zone.
- The panel reachable from CertAutoPilot over HTTPS (default
:2222). - The domain must resolve publicly — unless you set Zone Name (below), which skips the public-DNS zone lookup.
Credentials
Use your DirectAdmin username and password (a login key with DNS permissions is recommended over the account password). Scope the login key to only the rights needed and rotate it.
Add the credential
- Settings → DNS Credentials → New → DirectAdmin.
- Server URL:
https://da.example.com:2222. - Username + Password (or login key).
- Optionally Zone Name — the exact zone (e.g.
example.com) to operate in; set it to skip the public-DNS zone lookup (useful for internal/split-horizon domains). - Test (with a domain) → Save.
Config fields
| Field | Required | Purpose |
|---|---|---|
url | yes | DirectAdmin server base URL (default port :2222). |
username | yes | DirectAdmin login. |
password | yes | DirectAdmin password or login key. |
zone_name | no | Exact zone name; when set, skips the public-DNS zone lookup. |
Propagation
The record is written to DirectAdmin's DNS; propagation depends on the server's nameservers. Default settings usually work.
Troubleshooting
401 / login failed
Wrong username/password or login key, or the key lacks DNS (CMD_API_DNS_CONTROL) permission.
"Zone not found"
The domain isn't a zone on this server. If it is but the public-DNS lookup fails (internal domain), set Zone Name to bypass the lookup.