The Domain Nexus FOSSBilling adapter supports registrar operations with an API username/email and API key, or an advanced HMAC key ID and signing secret. Install the generated adapter without renaming its discovery file, and keep the selected secret in the server environment used by both web and scheduled PHP processes.
IN THIS ARTICLE
01 Prepare the account and environment
Download the FOSSBilling package published to your reseller account. Back up the installation and check the specific release's compatibility with your FOSSBilling version. The host's registrar interfaces can change between releases, so complete native order and synchronization tests before production use.
Issue the appropriate credential with the required domain permissions. For standard authentication, enter the API username/email and store the API key in the named environment variable. For advanced HMAC, leave email authentication unselected and enter the key ID with the signing-secret variable name. This adapter does not consume a one-time bootstrap form.
02 Install and configure
- Upload the generated contents of
library/Registrar/Adapterto the corresponding FOSSBilling directory. - Preserve both the generated discovery PHP filename and its adjacent implementation directory.
- Enable the adapter in FOSSBilling's domain registrar configuration.
- Enter the final HTTPS API endpoint and the fields for your selected authentication method. Secret fields receive the environment-variable name, not the secret itself. Our base is
https://my.nabtech.co/modules/addons/nabtechresellerdns/api/index.php. - Assign the intended TLDs and your retail prices, then perform an availability query.
03 Test realistic operations
Use a dedicated approved staging endpoint and credentials where available. The native sandbox switch does not create an upstream test environment; the supplied adapter refuses requests when that unsupported assumption is enabled.
Test registration, transfer, renewal, contacts, nameservers, lock and privacy. A transfer precheck does not prove eligibility: registry rules, source locks and authorisation codes still apply. Registry-specific data not represented by the host's native domain object needs the supported upstream or manual process.
04 Handle pending renewals carefully
Queued work remains pending until the provider outcome is known. Preserve the original order and operation references. Renewal uses the pre-renewal expiry as part of the business request; do not refresh that date and resubmit the same billed renewal as a new request.
After completion, run normal synchronization. The adapter refuses to silently truncate domains with more nameservers than its supported host representation. Investigate the actual domain configuration instead of accepting incomplete data.
Where do FOSSBilling customers manage DNS and forwarding?
This registrar adapter does not install a FOSSBilling DNS or forwarding customer tab. Use the reseller portal for those features. Registry deletion is disabled by default and should be enabled only for an explicitly approved workflow. For updates, preserve the environment configuration and verify both web and cron access after key rotation.