How to Create Private (Custom) Nameservers for Your Domain

Creating private nameservers involves two separate systems working together: your domain’s own DNS zone, and your domain registrar’s glue record registration. Here’s the practical walkthrough.

Step 1: Decide on the hostnames and IPs

Standard convention is ns1.yourdomain.com and ns2.yourdomain.com, each pointing at an IP address your DNS infrastructure actually answers on (commonly your hosting server’s IP, or a dedicated DNS cluster if you run one).

Step 2: Add A records in your DNS zone

In your domain’s DNS zone editor (cPanel’s Zone Editor, or wherever your domain’s DNS is currently managed), add:

• An A record: ns1 → your first DNS-serving IP
• An A record: ns2 → your second DNS-serving IP (ideally a genuinely different, redundant server)

Step 3: Register them as “child nameservers” at your registrar

This is the step people most often miss. Your domain’s registrar needs to know that ns1.yourdomain.com and ns2.yourdomain.com are valid nameservers before anyone can point a domain at them — this is done through a “child nameserver,” “glue record,” or “host record” section in your registrar’s control panel, entered separately from the DNS A records above. See our dedicated guide on registering glue records for this exact step.

Step 4: Confirm they actually answer DNS queries

Whatever server(s) those IPs point to must be running a DNS server (e.g. cPanel/WHM’s built-in DNS clustering, BIND, or PowerDNS) actually configured to answer authoritative queries for domains you’ll point at them — private nameservers only work if something is genuinely listening and answering on those IPs.

Step 5: Use them

Once steps 1-4 are confirmed working, update any domain (including this one, and any client domains) to use ns1.yourdomain.com / ns2.yourdomain.com as its nameservers, same as you would with any other nameserver pair.

A word of caution

Because glue records must resolve correctly before nameservers using them work at all, test with a low-stakes domain first if possible, rather than switching your main production domain’s nameservers before confirming the whole chain resolves correctly.