Rage4 authenticates this DNS connection with the account email and its API key. Although the provider's HTTP authentication uses the key in a password position, enter the provider API key in Domain Nexus, not the account's ordinary sign-in password.
IN THIS ARTICLE
01 Prepare the account
Obtain the Rage4 API key from the account authorised to manage your DNS. Check the account email carefully, particularly when a company has changed its contact address or operates several accounts. Record which zones and existing applications depend on the credential before replacing it.
Review provider-side features already attached to those zones. GeoDNS, failover and other advanced behaviour are not fully described by a basic portable record table. The Domain Nexus adapter reconciles the ordinary records it supports, so a migration should explicitly review provider-specific settings.
02 Connect and verify
- Add a Domain Nexus server and choose Rage4.
- Enter the exact Account Email and paste the provider credential into API Key.
- Save and run the connection check. It performs a domain-list request.
- Inspect an owned test zone's existing records before applying any template or bulk change.
- Add a distinctive temporary TXT record. Read it back after the operation completes, then remove that record and confirm its removal.
Common questions
Why can the module list domains but not use a particular one?
A provider inventory and a customer's local entitlement are different checks. Verify both that the credential has provider access and that Domain Nexus has linked the zone to the correct customer. Do not grant every WHMCS customer access to everything visible under the shared Rage4 account.
Should I retry when the provider response is unclear?
Read the task and provider state first. The adapter refuses an invalid record-list response rather than treating it as an empty zone, because a false empty inventory could lead to destructive reconciliation. Capture that error and restore reliable reads before submitting another change.
Finally, compare the registrar's nameservers with the Rage4 service. API access proves management connectivity; authoritative queries establish whether the internet is using those records.
Related articles
- Discover existing DNS zones and link only verified customer ownership
- Resolve DNS drift and changes with an unknown provider outcome
- Run a controlled DNS provider acceptance check before assigning customer packages
- Connect Zonomi and identify the zones authorised by its API key
- Connect DigitalOcean DNS with domain-specific API scopes
- Connect InterWorx DNS with a NodeWorx API key