Ask whether your account may list its zones, read complete record sets, create zones, update records, delete zones and manage DNSSEC keys. These permissions can differ. An account restricted to existing zones may still be useful, but a product that automatically creates a zone needs the corresponding provider permission and allowance.

Confirm whether the API key is restricted to your tenant and which network addresses may use it. Keep the supplier's quota and support reference with the connection's operational notes. Do not enter a customer-facing DNS hostname as an API address unless the supplier explicitly uses it for both roles.

1. Add a server in Domain Nexus and select PowerDNS Hosted.
2. Enter the supplied Hosted API URL as the origin or approved proxy prefix. The adapter adds the standard /api/v1/servers/{serverId} path.
3. Paste API Key and set Server ID to the supplier's exact value.
4. Enter the assigned authoritative hostnames in Default Nameservers. Keep these consistent with your DNS package and any supplier-supported vanity nameservers.
5. Save, run the check and test an authorised zone. Confirm that listing does not expose an unrelated tenant's resources before customer onboarding.

Test a temporary TXT update and a provider readback. If the account permits creation, also verify one disposable test zone lifecycle. If it does not, adopt only precreated, ownership-verified zones and keep creation disabled in the customer workflow.

For DNSSEC, verify which key operations the hosted API supports and who publishes the parent DS. For replication, check the record types supported on every selected target. A hosted connection's availability in a package does not make all provider features portable or guarantee that the supplier accepts every operation.

• Connect the PowerDNS Authoritative API to Domain Nexus
• Synchronize a DNS package across multiple servers and select its master
• Run a controlled DNS provider acceptance check before assigning customer packages
• Build a DNS package for hosting products, addons and domain TLDs
• Resolve a FOSSBilling nameserver set that exceeds its local contract
• Plan a WiseCP integration using the current API when no native connector is supplied

• PowerDNS: Authoritative HTTP API