Sign in as the account that will own the managed DNS zones. Open its Access keys area and add a dedicated key. Enable the DNS commands required by your intended workflow under Hestia's API access rules. An account limited to reading records cannot create zones or apply customer changes. Keep the access key ID and secret together, and record which installation uses them.

1. In Domain Nexus, open Servers, add a server and choose HestiaCP DNS.
2. Enter the server's hostname in Hostname or IP address. A bare hostname uses port 8083; use a full HTTPS URL when the panel uses another port.
3. Enter the exact HestiaCP username, Access key ID and Secret key. These are separate fields, not a single combined password.
4. Review Default zone IPv4 address. It seeds new zones, so use the intended public service address. An automatic server-address fallback is not necessarily your customer's website address.
5. Save and run the available connection check. Add the connection to a test DNS package before using it for paid products.

Create one authorised test zone, read its records, add a temporary TXT record, read it back and remove that record. Check the same account in Hestia. If the package uses external authoritative nameservers, confirm the zone is actually served there before changing a customer's delegation.

A failure to connect usually calls for checking the panel hostname, certificate, firewall and API access settings. A successful connection followed by a rejected edit calls for checking the user's DNS permissions and zone ownership. Do not solve an ownership error by moving unrelated accounts under the integration user. DNSSEC controls depend on the installed adapter and zone capabilities; the current Hestia connection does not provide a signing-key workflow.

• Add a DNS provider connection and prove that it can manage zones
• Build a DNS package for hosting products, addons and domain TLDs
• Run a controlled DNS provider acceptance check before assigning customer packages
• Connect cPanel or WHM DNS using an existing WHMCS server or dedicated token
• Connect Plesk DNS with the correct administrator API access

• HestiaCP: REST API