Sign in to NodeWorx and open NodeWorx > API Key. Obtain or generate the authorised key. Before regenerating an existing one, inventory the billing systems, DNS peers and other integrations that use it. InterWorx's key regeneration requires replacing the old value in those applications.

Confirm that the account can use the DNS operations required by your package and that the WHMCS server can reach the HTTPS panel endpoint. Keep any source-network restriction aligned with both web and cron execution.

1. In Domain Nexus Servers, choose InterWorx NodeWorx DNS.
2. Enter Hostname or IP address. The default for a bare hostname is port 2443; use a full HTTPS URL for a custom endpoint.
3. Paste NodeWorx API key.
4. Review Default zone IPv4, optional Default zone IPv6 and SOA contact email. These seed new-zone data and should reflect the intended service.
5. Save and run the check. Use a controlled package to read an owned zone, add a temporary TXT record and verify the completed result.

The connection can fall back to the server's address when the default IPv4 is omitted. That may suit your deployment, but a panel hostname is not automatically the correct website destination for every customer. Review package record sets and the intended website and mail addresses before provisioning.

The key has its own lifecycle and can remain unchanged when the user's sign-in details change. Rotate or revoke the key explicitly when retiring access, and update every authorised dependent connection. Verify that DNS still reads and writes after the replacement, especially from scheduled jobs.

• Rotate a DNS provider credential across all connections that use it
• Create DNS record sets that become package defaults
• Run a controlled DNS provider acceptance check before assigning customer packages
• Connect Rage4 DNS without confusing its API key with an account password

• InterWorx: Manage API keys