The DirectAdmin adapter manages records in DNS zones already available to its authenticated account. This build does not create or delete standalone DirectAdmin zones. Prepare the domain in DirectAdmin first, then link the verified zone to the correct customer in Domain Nexus.
IN THIS ARTICLE
01 Create a restricted login key
Use DirectAdmin's login-key facility for the intended admin, reseller or user account. Limit the key to the commands and source addresses required for the integration. The current adapter checks domain visibility with CMD_API_SHOW_DOMAINS and manages records through CMD_API_DNS_CONTROL. A key limited only to a different DNS API command may fail even if its name suggests DNS access.
Do not grant key-management commands merely to make a DNS key work, because those commands can undermine the intended restriction. Confirm the account itself is authorised for the domain. A key cannot grant its account ownership of another customer's zone.
02 Add the server
- Choose DirectAdmin under Domain Nexus Servers.
- Enter Hostname or IP address. A bare hostname uses port 2222; use a full HTTPS URL for a different panel endpoint.
- Enter Username and the dedicated key in Password or login key.
- Save and run the connection check. Inspect the authorised domain list.
- Link an existing owned zone and test a temporary TXT update, then read the provider's records and public authoritative answer.
Common questions
Why does new-zone provisioning say the domain must exist first?
The installed adapter exposes existing-zone record management. Create or provision the domain through the appropriate DirectAdmin hosting workflow, verify ownership, and then adopt its zone. Changing the provider connection to a more privileged username does not add a missing adapter operation.
Can this connection be a replication target?
Use it only when the intended target zone already exists, is authorised and has a verified binding. Check the record types supported by all selected package servers. Provider replication does not create a DirectAdmin hosting account or copy its website files.
Keep DNSSEC signing administration separate where it is performed in the panel, because this adapter does not expose a DNSSEC management workflow.