Skip to content

Knowledgebase

Connect cPanel or WHM DNS using an existing WHMCS server or dedicated token

domain-nexus, whmcs

Domain Nexus can reuse a cPanel server already configured in WHMCS or connect with a dedicated WHM username and API token. A WHM reseller credential is supported within its actual zone permissions. Root access is not a requirement for every DNS workflow, and an API token cannot grant permissions its owner does not have.

01 Choose the connection method

  1. Open Domain Nexus Servers, add a connection and choose cPanel / WHM.
  2. To reuse a WHMCS server, select it in WHMCS cPanel server. Confirm its address and account refer to the intended machine. The module can use its stored connection details.
  3. For a dedicated connection, enter Hostname or IP address, WHM username and API token or password. Prefer a separately revocable WHM API token with the necessary DNS privileges.
  4. Review Default IP for new zones. An omitted value can use the linked server's address, so confirm it is suitable for the initial zone.
  5. Leave cPanel Account Username empty unless you intend to park DNS-only domains as aliases under an existing cPanel account.
  6. Save and check the connection, then test an owned zone read and temporary TXT change.

02 Match permissions to the actual task

A connection that reads zones may still lack privileges to add records, create zones, manage DNSSEC or create a parked alias. Prepare the WHM token against cPanel's current API privilege reference and the operations you will enable. For a reseller, confirm the target zone belongs to that reseller's permitted scope.

What belongs in cPanel Account Username?

Enter the existing cPanel account username, not its primary domain or the WHM login name. It is an optional DNS parking target. The dedicated parking guide explains how eligible DNS-only domains become aliases while hosted domains and ownership conflicts remain protected.

Why did typed details behave differently from the selected server?

Explicit connection values can override details supplied by the linked WHMCS server. Review a stale typed host, username or secret before assuming the WHMCS server record is wrong. Keep the linked server association accurate when using automatic hosting handoff, and test the DNS and hosting workflows separately.

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support