Private nameservers such as ns1.example.com and ns2.example.com let customers use nameservers under your own domain. The registrar, authoritative DNS service and WHM defaults must agree for the setup to work.
IN THIS ARTICLE
Check access and requirements
Obtain the nameserver IP addresses and supported naming arrangement from us. You must control the domain used in the nameserver names and have access to its registrar. Do not invent a second IP address or assume the website address is also a DNS server.
01 Set up private nameservers for a WHM reseller
- At the registrar of
example.com, create the required child-host or glue records for each nameserver using the supplied IP addresses. A normal DNS A record alone is not the same as registrar glue. - In the authoritative zone for example.com, create matching address records for the nameserver hostnames. Check both A and AAAA records when IPv6 is used.
- In the WHM nameserver settings available to your reseller role, enter the approved nameservers. The server administrator may need to set these under reseller nameserver privileges if you cannot edit them.
- Confirm that the DNS service is authoritative for the customer zones before changing a customer domain delegation. Keep the previous DNS service available during a planned migration.
- At each customer domain registrar, set the intended nameserver delegation. Changing WHM defaults does not automatically change registrations at external registrars.
02 Checklist: keep each nameserver configuration layer consistent
| Configuration layer | What must agree |
|---|---|
| Registrar for your nameserver domain | The required child-host entries, such as ns1.example.com, use the IP addresses supplied for your DNS service. |
| Authoritative DNS for the nameserver domain | The nameserver hostname address records match the intended assigned addresses. |
| WHM or reseller defaults | The nameserver hostnames match the approved branded names. |
| Each customer domain registrar | The domain delegation names those servers after its zone is ready there. |
The names are illustrative. Use the exact names and addresses approved for your service. A saved WHM default does not create registrar glue or update every customer registration, so verify each layer before moving live DNS.
How do I verify private nameserver delegation?
Check delegation and query the new authoritative nameservers directly for the domain. Verify website, MX and important TXT records, not only the home page. Allow for existing DNS cache lifetimes.
Resolve setup problems
If results differ between resolvers, compare registrar glue, address records and zone contents. A nameserver address that responds to ping is not proof of working DNS. Send support the domain, nameserver names and query results without account passwords.
.png)
 (1).jpg)
 (1) (1).png)
 (1).png)
.jpg)
.jpg)
 (1).jpg)
.jpg)
