Skip to content

Knowledgebase

Choose Domain Nexus client navigation, themes and translations

domain-nexus, domains-dns

Domain Nexus lets you choose how customers enter DNS management and how the module looks in administrator and client areas. Configure these settings around your WHMCS theme and support documentation, then test with an ordinary customer account.

01 Choose the client experience

  1. Open the client-experience settings and choose Advanced, WHMCS Native or Both.
  2. Use Advanced for the dedicated DNS workspace, WHMCS Native to mount module DNS management within the native domain page, or Both when customers should have both routes.
  3. Set the customer-facing DNS label where available. Use the same wording in your welcome emails and knowledgebase.
  4. Save and test navigation from Domains > My Domains and the account-wide DNS entry.

The advanced all-zone entry is normally placed under Domains, with a Services fallback for themes without that menu. Native-only mode hides the separate advanced entry. A missing menu can therefore be an intentional experience setting rather than a provider failure.

02 Select visual settings

Administrator and client themes can be configured separately. The current theme set includes Command Center, Executive, Midnight, Aurora Studio, Ocean Breeze, Forest, Rose Quartz, Graphite Gold and WHMCS Native. Use the appearance preview to inspect cards, text, accent colours and navigation before saving.

Choose readable contrast and check the mobile layout, long domain names and validation messages. Colour customisation should not make success, warning and error states indistinguishable. Avoid changing vendor module files merely to achieve a setting already exposed in the interface.

03 Translate the actual workflows

Use Workspace > Translations and the release's supported language-file process for your customers' languages. Translate action meanings consistently, particularly DNSSEC, deletion, pending requests and restore. Preserve placeholders and variable syntax.

Review both administrator and customer surfaces. A translation that works for a short button can be unclear in a confirmation message. Test a refused action so the customer receives a meaningful explanation in the selected language.

Can a theme change make a restricted DNS feature available?

Menus also depend on service controls, package entitlements and the current user's permissions. A theme change should not be used to expose an action a package does not allow. Test a hosting client, a domain-only customer and a reseller separately.

After upgrades, review changed labels and new language keys. Update screenshots only when they match the installed version; text instructions should remain usable if a theme moves a menu within the same supported workflow.

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support