How to Use Your Own Nameservers as a cPanel Reseller
Last updated Changelog
On this page
By default your customers point their domains to NameCrane’s nameservers, ns1–ns4.private-nameserver.net. With your own nameservers they use names on your domain instead, such as ns1.yourbrand.com. These names point to NameCrane’s global DNS servers, so DNS works exactly the same; only the names change.
In this example our demo reseller uses its own domain, cpanel.cranedemo.com, so its nameservers are ns1.cpanel.cranedemo.com to ns4.cpanel.cranedemo.com.
Before you start
Your nameservers must point to the same addresses as ours:
| Your nameserver | Points to |
|---|---|
| ns1.yourbrand.com | 205.185.112.66 |
| ns2.yourbrand.com | 194.177.13.4 |
| ns3.yourbrand.com | 199.195.255.66 |
| ns4.yourbrand.com | 194.177.13.4 |
These are the addresses of ns1–ns4.private-nameserver.net. To check them yourself, run dig +short ns1.private-nameserver.net (and so on for ns2–ns4).
Steps
-
Register the names at your domain registrar. Log in where your domain is registered and create each nameserver with its address from the table. Registrars call these child nameservers, glue records, host records or private nameservers. This is what lets other domains use your names as their nameservers.
-
Add the same names to your domain’s DNS. If your domain’s DNS is hosted with us, log in to your own cPanel, open Zone Editor and click Manage next to your domain. Add an A record for each name (
ns1→205.185.112.66, and so on). See Add or change a DNS record. If your DNS is hosted somewhere else, add the A records there.
-
Set them as your nameservers in WHM. Log in to WHM, type
Basic WebHostin the menu search and click Basic WebHost Manager® Setup.
-
Under Nameservers, choose Explicitly Set the Nameservers and fill in Nameserver 1 to Nameserver 4 with your names. Click Save Changes.

-
WHM confirms Your account’s nameservers have been set to your four names. Every account you create from now on lists your nameservers in its DNS zone.

-
Check that your names work before you give them to customers. Run
dig +short ns1.yourbrand.comfor each name, or look them up at whatsmydns.net. Each should show its address from the table. Ours worked within minutes, but a new registration can take a few hours to show everywhere.
Now tell your customers to set their domain’s nameservers to ns1.yourbrand.com to ns4.yourbrand.com at their registrar.
Note: Accounts you created before the change keep their old nameserver records. That’s fine, because both sets of names point to the same servers. To go back to NameCrane’s names for new accounts, choose Inherit Nameservers from root and save.
Troubleshooting
| Problem | What to do |
|---|---|
My registrar won’t accept ns1.yourbrand.com as a nameserver |
Register it as a child nameserver first (step 1), using the domain those names belong to. |
ns1.yourbrand.com doesn’t resolve |
Check the A records (step 2) and the child nameservers (step 1). Then give it a few hours. |
| New accounts still show the old nameservers | Check that Explicitly Set the Nameservers is chosen and that you clicked Save Changes. The setting only affects accounts you create afterwards. |
| A customer’s site stopped working after they switched | Make sure all four of your names resolve to the right addresses. Until they do, have the customer switch back to ns1–ns4.private-nameserver.net. |
Snagged on something? Contact support and we’ll get you sorted.