Prepare API access in the ClouDNS account. If using a sub-user, assign the domains and permissions that the connection needs, and review its zone and record limits. Sub-user access does not imply the same resource visibility as the master account.

The module accepts API user ID, Sub-user ID or Sub-user name. The sub-user name takes precedence when present; otherwise the sub-user ID is used before the master API user ID. To avoid an old field silently selecting another identity, fill in the intended option and clear the unused alternatives.

1. Add a Domain Nexus server with provider ClouDNS.
2. Enter the chosen identity and its API password.
3. Review optional Default nameservers. These are used when registering a new master zone and must match the service you intend to publish.
4. Save and run the connection check. Inspect the zones visible to this identity.
5. Test a temporary TXT change in an authorised zone. If the package will create zones, also verify creation within the sub-user's quota.

Compare the sub-user's password, assigned zones, access restrictions and remaining allowance. Check that the form has not retained a higher-precedence sub-user name from an earlier configuration. Grant the missing intended access rather than replacing every scoped connection with the master credential.

No. The adapter can use the provider's DNSSEC operations where allowed, but the parent DS still needs to correspond to the provider's actual keys. Check both signing and public validation. A zone configured as a secondary also requires the correct primary and transfer permissions; it should not be treated as an ordinary editable master simply because the account lists it.

• Set DNS package limits and customer permissions without blocking the wrong service
• Operate DNSSEC from zone signing through parent DS verification
• Configure secondary DNS with an authorised transfer source
• Run a controlled DNS provider acceptance check before assigning customer packages

• ClouDNS: Access and authentication