Panels & Zone Editors
WHM is where a platform's nameservers get their names
WHM has accepted ns1 and ns2 on your own domain and the client name still will not resolve.
The short answer
WHM is the tier above cPanel, where accounts are created, packages defined and server-wide policy set — and the field a name holder cares about is the pair of nameserver hostnames WHM hands to every new account, because that is the delegation clients will be asked to use.
Typing ns1.yourbrand.com into WHM does not create a nameserver at the registry. It tells this server what to call itself. The glue that makes the hostname resolvable is registered at your registrar, for your own domain, and it is a separate job.
By the Hosting & Domains team · Reviewed 18 August 2026
100+
Terms defined for people who hold names
2 min
To read, at an unhurried pace
Plain
English, with the registry jargon translated
24/7
Cover on the support desk, all year
A cPanel account holds one customer's world. WHM governs the accounts themselves — creating, suspending, resizing, building package templates — along with server-wide settings such as the nameserver hostnames and the DNS zone template new accounts inherit.
That division is the reseller model expressed as software, and it is also where the DNS responsibility divides. WHM decides what the platform tells the world its nameservers are called. Only the registry can make that name resolve.
The nameserver fields, and what they do not do
Basic WebHost Manager Setup carries the nameserver hostnames the platform will offer. Fill them in and every account created afterwards is told to use them, and clients are given them to enter at their registrars. Nothing in that process contacts a registry.
The missing half: at the registrar for yourbrand.com, register ns1 and ns2 as host records with the server's addresses. The registry then publishes those addresses as glue alongside any delegation to them. Without it, resolvers are asked to find ns1.yourbrand.com using ns1.yourbrand.com, and only cached answers work.
The zone template every new account inherits
WHM holds a template that decides which records a newly created zone starts with — the A record, the www record, the mail records, the SPF entry. Change the template and only accounts created afterwards get the new version; existing zones keep whatever they were built from.
That is worth knowing before a mass change. Adding a record to the template does not add it to two hundred existing zones, and discovering that one client at a time is the slow way to learn it.
Account creation and removal both touch DNS
Creating an account writes a zone for its name on this server. Terminating an account deletes that zone. Where the name is delegated here, deletion means the name stops resolving the instant the account goes — which is correct behaviour and still a shock when the client had asked only to cancel hosting.
So the order for a client leaving is: let them re-delegate the name to its new home first, confirm it resolves there, and terminate afterwards. Terminating first turns a planned move into an outage.
Why two hostnames on one server is not redundancy
WHM will accept ns1 and ns2 pointing at the same machine and the platform will work perfectly until the machine reboots, at which point every name delegated to it goes dark at once. Two names, one failure domain.
DNS clustering exists for exactly this: two servers, each authoritative for the same zones, kept in step so that either can answer alone. Short of that, a secondary DNS service costs little and turns a reboot back into a reboot.
The half of private nameservers that lives at a registrar
WHM documentation ends at its own text fields, and registrar documentation begins after them, so the join between the two is where private nameservers usually fail. This glossary treats that join as the actual subject.
Order an annual plan and the first year of the name's registration is included.
- Written by the people who answer the transfer tickets
- Locks and grace periods given in days, not folklore
- Panel screens named, so you know where to click
- Open to read, with no account and no mailing list
Why Hosting & Domains
Standard on every plan
Panel field against registry record
What the nameserver boxes in WHM actually do, and which separate job makes those hostnames resolvable.
Registry, registrar and host kept apart
Every entry names which party actually controls the thing described, because mistaking one for another is where most lost afternoons begin.
Zone templates and their blind spot
Why a template change reaches new accounts only, and what that means for a platform already carrying clients.
Written from the transfer queue
These are the answers our own desk gives when a name stops resolving on a Friday, not a rewrite of somebody else's help centre.
Termination treated as a DNS event
The order that lets a client leave without their name going dark between suppliers.
The command that settles it
Where a claim can be checked from outside — dig, whois, a resolver you do not control — the check is written out in full.
Quick Start
Order placed to site online
- 1
Register the host records at your registrar
ns1 and ns2 as host records for your own domain, with the server's addresses, so the registry publishes glue.
- 2
Fill the nameserver fields, then test with a spare name
Delegate a name you can afford to break, query it from an outside resolver, and only then hand the hostnames to a client.
- 3
Re-delegate before you terminate
Let the client's name point at its new home and confirm it resolves there. Deleting the account deletes the zone with it.
Built In
Fitted to every plan
- Webmail in the browser, with IMAP, POP and SMTP for any client you prefer
- The latest cPanel, with people on the support desk at any hour
- Your site lifted off the old host and set down here, at no charge
- SSH on the developer plans, Git and Composer already installed
- 99.9% uptime as the target, watched around the clock
- Thirty days money back on hosting plans, seven on reseller
- Upgrades applied in place, so changing plan is not a migration
- Hosting renewed at the rate you ordered at, year after year
- The auth code issued from your client area, with no retention call to sit through
- Mailboxes on your own name included, not sold back at the checkout
Frequently Asked
Questions we field again and again
I set my nameservers in WHM but clients' domains will not resolve. What is missing?
The registrar half. WHM only tells the server what to call itself; the hostnames ns1 and ns2 must also be registered as host records at the registrar for the domain that carries them, so the registry publishes their addresses as glue. Until that exists, a resolver has no way to find your nameserver except by asking your nameserver, and only clients whose resolvers already cached an answer will appear to work.
If I terminate an account in WHM, what happens to the domain name?
The registration is untouched — that lives at the registry and belongs to whoever the registrant field names. What disappears is the zone this server was holding for it, so if the name was delegated here it stops resolving immediately. Have the name re-delegated to its new nameservers and confirmed working before the account is terminated, and the change is invisible to visitors.
How soon after registering can a name be moved?
Not within 60 days of a registration or of a previous transfer. That clock belongs to the registry rather than to us, so no amount of goodwill at either registrar shortens it. Plan a move around the date and the transfer is paperwork; ignore it and the request is simply refused.
Who is the registrant of a name ordered through you?
You are. The name is registered in your own details, stays registered in your name for the term you have paid for, and can move to any registrar once the standard 60-day window has passed. A supplier that registers your name in its own details has taken the asset, whatever the invoice says.
Keep reading
Domain Names
Names registered, transferred and renewed, with the first year included on an annual plan.
VPS Hosting
A VPS instead, where the address, the reverse DNS and the nameservers are yours to run.
Changing provider? Work through this checklist beforehand.
A straightforward running order for a migration your visitors never spot: which files travel first, how to bring the mail across without dropping a single message, the right moment to repoint DNS, and the two errors that sit behind almost every outage we get called in to fix.
Nameservers in your name, glue at the registry.
From one website to a rack of machines, moving up is a change to the account rather than a migration.
View Domain Names plans