The Vultr DNS connection uses a provider API key and must pass Vultr's access-control rules. A common setup failure is allowing the administrator's laptop address while the actual request comes from the WHMCS web server or a background worker.
IN THIS ARTICLE
01 Prepare the allowed caller
In the Vultr account's API access settings, enable the authorised integration credential and configure the permitted source addresses. Determine the actual outbound public address used by WHMCS, including any network address translation. If web requests and cron run through different egress addresses, account for both under your approved access policy.
Use the current account or organisation permissions to limit the integration appropriately. Avoid assuming every Vultr account exposes identical key-management options. Record the key owner and the installations that depend on it before rotation.
02 Add the provider
- Open Domain Nexus Servers and select Vultr DNS.
- Paste the provider credential into API key.
- Review Default zone IP. Supplying it seeds an apex address record during zone creation. Leaving it blank creates the zone with its provider NS/SOA set, allowing your package record set to supply the intended services.
- Save and run the connection check from the real installation.
- Test an owned zone read and a temporary TXT edit. Verify background execution as well as the browser-triggered request.
Why does the browser check work while scheduled DNS jobs fail?
Check whether the worker uses a different outbound IP, network path or stored connection. Review the job's provider response and the current API access-control list. The customer's source IP is not the relevant address when Domain Nexus makes the request on the server.
Can I infer DNSSEC is active because the provider supports it?
No. The zone needs a completed signing operation and the correct parent DS. Verify both with the DNSSEC workflow. Also confirm the registrar delegates to the actual Vultr DNS nameservers after a migration. Authentication and zone creation establish management state; authoritative queries establish the public DNS result.
Related articles
- Rotate a DNS provider credential across all connections that use it
- Keep Domain Nexus jobs, scheduled DNS changes and reconciliation running
- Operate DNSSEC from zone signing through parent DS verification
- Run a controlled DNS provider acceptance check before assigning customer packages
- Connect OVHcloud DNS with region-matched application and consumer keys