The WHM default nameservers provide nameserver values for account provisioning on the server. Setting these defaults is one part of a working DNS setup; it does not update external registrar delegations for existing domains.
IN THIS ARTICLE
Check access and requirements
This is a server-administration task unless your reseller privileges explicitly expose the appropriate settings. Obtain the approved authoritative DNS hostnames and addresses. Confirm the registrar glue, DNS service and relevant zones are already planned.
01 Set the default nameservers in WHM
- Log in with the authorized administrative account and open Server Configuration > Basic WebHost Manager Setup.
- Record the current nameserver values before changing them. Determine whether resellers use separate nameserver overrides.
- Enter the intended fully qualified nameserver names in the nameserver fields. Use hostnames such as
ns1.example.com, not a URL or directory path. - Review address-record options carefully and save the configuration. Make matching address records in the authoritative zone and registrar child-host records where required.
- Create a controlled test account or inspect the next approved provisioning operation to verify the nameservers used. Plan any existing-domain changes separately.
How do I verify the default nameserver settings?
Query each nameserver directly for a test zone and check public delegation through the registrar. Verify the zone has the intended website and email records. A saved default is not sufficient evidence that the DNS service is responding.
Resolve setup problems
If newly created accounts still use different nameservers, check reseller-specific settings and external provisioning configuration. If delegation fails, compare glue and authoritative address records. Preserve the old working DNS service during a migration so you can correct a mismatch without leaving customer domains unresolved.