The OpenProvider DNS connection signs in to Openprovider's REST API with an API-enabled contact's username and password, then uses the returned bearer token internally. You configure the durable account credential in Domain Nexus, not a temporary token copied from an earlier API response.
IN THIS ARTICLE
01 Enable the correct contact
In the Openprovider control panel, open Account overview, then Contact persons. Add or select the intended contact, open its API tab and enable API access. Confirm the account can manage the desired DNS service. Registrar contracts and domain-registration permissions are separate from the DNS-zone access used here.
Use a dedicated authorised contact where your provider account permits it. Keep its identity and access changes documented, because changing its password or disabling API access also affects background DNS jobs.
02 Configure and validate
- Add a Domain Nexus server using provider OpenProvider.
- Enter the contact's Username and Password.
- Review API Base URL. The live default is
https://api.openprovider.eu/v1. Use a different environment only with the matching authorised account and documented endpoint. - Save and run the connection check, which authenticates and performs a DNS-zone list read.
- Read an owned zone and make a small temporary TXT change. Check the final provider record before enabling automatic provisioning for a package.
Common questions
Does connecting DNS enable Openprovider as my WHMCS registrar?
No. This server connection manages DNS. Your registrar routing, commercial account and registration requirements have their own configuration. Domain Nexus can use different providers for a registration and its authoritative DNS.
Why can I sign into the provider website but the connection fails?
Check that API access is enabled for this exact contact, not simply another contact on the account. Confirm the password, API environment and any account restrictions. If authentication succeeds but a zone is absent, review the provider account and zone ownership rather than creating a duplicate blindly.
Before importing an existing domain with a multi-label extension, inspect the provider's returned domain and zone identity. Keep the actual authoritative nameservers with the migration record so that a correct API configuration is also connected to the public DNS service.