Private nameservers are the single most client-visible piece of white-label reseller hosting, and also the piece most often set up slightly wrong — not broken exactly, but incomplete in a way that surfaces the underlying provider anyway. This is a precise, technical walkthrough of doing it correctly the first time.

What a Private Nameserver Actually Is

A private (or "custom" / "vanity") nameserver is simply a nameserver hostname under your own domain — ns1.yourbrand.com and ns2.yourbrand.com — that points to the same underlying DNS infrastructure your reseller provider already runs, just labeled with your brand instead of theirs. Functionally, it resolves DNS exactly the same way a generic ns1.providername.com would; the only difference is what a client sees when they check their domain\'s nameserver settings.

Step 1: Choose Your Nameserver Hostnames

The standard convention is two hostnames: ns1.yourdomain.com and ns2.yourdomain.com. Some resellers use three or four for redundancy branding purposes, but two is the accepted minimum and standard for most setups.

Step 2: Register the Nameservers in WHM

In WHM, under nameserver/DNS settings, register your chosen hostnames as private nameservers, associating each with the specific IP address your provider has assigned to your reseller account. This step tells your own server "these hostnames belong to you and should resolve to these IPs" — but it does not yet make the wider internet aware of that.

Step 3: Create Glue Records — The Step Most Often Missed

This is the step that actually makes your private nameservers work from the outside world\'s perspective. A glue record is an A record for the nameserver hostname itself, registered at the domain registry level (not just in your own DNS zone) — because a nameserver hostname that lives on the same domain it\'s serving DNS for creates a chicken-and-egg problem: to look up ns1.yourdomain.com, you\'d normally ask yourdomain.com\'s nameservers, which is ns1.yourdomain.com itself.

Glue records solve this by publishing the nameserver\'s IP address directly at the registry level, alongside the domain\'s own nameserver delegation. You typically set these up in your domain registrar\'s control panel under a "nameserver management" or "child nameserver" / "glue record" section — the exact location varies by registrar, but the concept is universal across all of them.

Step 4: Point Your Domain at Your New Nameservers

Once glue records are live, update your own primary domain\'s nameservers to ns1.yourdomain.com / ns2.yourdomain.com at your registrar. Test this on your own domain first, before rolling it out to any client domains — it is much easier to debug a propagation issue on a domain you fully control.

Step 5: Allow for DNS Propagation

Nameserver changes are not instant — propagation across the global DNS system typically takes a few hours and can take up to 24-48 hours in some cases, depending on TTL (time-to-live) settings and how quickly various resolvers worldwide refresh their cached records. Don\'t judge a nameserver change as "broken" within the first few hours; verify using a DNS propagation checker across multiple global locations before troubleshooting further.

Step 6: Roll Out to Client Domains

Once your own domain confirms working correctly on the new nameservers, use the same ns1.yourdomain.com / ns2.yourdomain.com pair for every client domain going forward — this is where the initial one-time setup work pays off, since no further nameserver-level configuration is needed per client.

Common Mistakes That Leave the Setup Half-Working

  • Skipping glue records entirely — nameservers appear configured in WHM but never actually resolve correctly from the outside world
  • Only creating one glue record instead of two — leaves you without proper nameserver redundancy, a real reliability risk if one resolves and the other doesn\'t
  • Forgetting to update glue records if your IP ever changes — a server migration or IP reassignment silently breaks nameserver resolution for every client until glue records are updated to match
  • Testing on a live client domain instead of your own first — turns a debugging exercise into a client-visible incident unnecessarily

How This Fits Into Full White-Labeling

Correctly configured private nameservers are the foundation of white-label reseller hosting — everything else (branded cPanel login, branded invoices, your own support contact) matters, but nameservers are the first and most technical thing a client\'s domain registrar will ever show them, and the one piece that, if wrong, undermines the whole white-label effort regardless of how polished everything else looks.

WebsNP\'s reseller hosting onboarding includes guided private nameserver setup, including glue record configuration, so your brand — not ours — is what every client sees from day one. See our reseller hosting plans for details.