Domain Nexus brings domain resale, DNS management, domain forwarding and email forwarding into WHMCS. Start by deciding which services your company will operate and who will use them. Your hosting customers can manage entitled domains in the client area, while resellers receive a separate portfolio, wallet and integration workspace.
IN THIS ARTICLE
01 Map services to the right audience
Ordinary hosting customers do not need reseller membership merely to edit DNS. Their access can come from an active hosting product, product addon, registered domain or an explicitly configured allowance. Reseller accounts add commercial ordering and API functions. A company buying the module administers the installation, its providers and policies; buying a Nabtech hosting service does not itself provide those administrator privileges.
- List the services you intend to sell: domain registration, managed DNS, Premium DNS, web redirects or email forwarding. Enable the relevant service controls independently.
- Identify authoritative DNS providers, registrar connections and forwarding infrastructure. A DNS provider connection does not become a domain registrar connection.
- Design DNS packages around actual products, addons and TLDs. Decide zone limits, record limits, allowed record types and customer controls before automatic creation starts.
- Choose the client experience: Advanced, WHMCS Native or Both. Consider your support guides and existing domain navigation when selecting labels.
- Decide whether you will operate reseller groups, prepaid funding and downloadable billing-platform connectors. Confirm the upstream registrar permissions and supported TLD operations.
02 Build a small acceptance portfolio
Use domains and hosting accounts you control to verify a normal hosting customer, a domain-only customer and a reseller. Test a DNS record change, renewal workflow, permission refusal and a provider failure. Include a domain using external nameservers so your staff can distinguish an editable stored zone from the zone answering publicly.
Review Readiness & diagnostics, Jobs & runtime and the relevant service pages before launch. Successful provider authentication is only the first check. Record creation, worker completion and authoritative answers must also agree.
Who should control zone ownership and approve DNS recovery?
Keep a record of who controls registrar accounts, DNS provider credentials, encryption-key backups and the WHMCS cron. Assign a support procedure for disputed ownership, failed paid operations and DNSSEC migrations. These cases require careful reconciliation rather than repeated provisioning.
Document the features you actually enabled for each package. The module supports multiple provider types and commercial options, but customers should see guidance for their entitlement and the capabilities of their domain's backend.