How to Create Private Nameservers (ns1.yourdomain.com)

What private nameservers are

Private nameservers — ns1.yourbrand.in and ns2.yourbrand.in — are nameservers named under your own domain, and resellers need them for supply-chain anonymity. The three-part setup:

1. Glue records at your registrar — register ns1/ns2 as host records pointing at your server's two DNS IPs.
2. Nameserver configuration in WHM — Basic WebHost Manager Setup, replace defaults with your ns1/ns2, accept the A-entry writes.
3. Point client domains — set each client domain's nameservers to your ns1/ns2 at their registrar.

The technical wrinkle is circularity: finding yourbrand.in's DNS requires the glue to exist first, which is why the registrar step comes before everything. Resellers on managed plans skip step 2 — the host pre-brands the nameservers.

Why resellers need them

Why resellers need them. Do the change this heading names on one site first, then check it in a private browser window or in the mail client, depending on the topic. Change one setting at a time, and undo it if the result is wrong before you try the next. If you want the Jaipur desk to look with you, email support@webji.services — that mailbox is staffed 24/7 in Hindi and English. Phone +91 141 4941811 is business hours only.

Step 1: A records at your registrar

How this plays out with glue records: settings that look cosmetic usually decide page speed and uptime under real traffic. The defaults WebJi® ships are tuned for Indian network conditions, and support can review your setup on request.

Step 2: registering glue records

registering glue records. Do this on one site or a staging copy first, then check the public URL in a private window so cache does not hide the result. Stop if the page errors, and email support@webji.services with the step name and the exact error before you repeat it on every account. WebJi® support mail is staffed 24/7 in Hindi and English; the phone line +91 141 4941811 is business hours only.

Step 3: nameserver setup in WHM

Step two, nameserver configuration in WHM (cPanel servers and reseller WHM access). Open WHM Home, Service Configuration, Nameserver Selection and confirm BIND (or nsd) is the chosen DNS service.

Then WHM Home, Server Configuration, Basic WebHost Manager Setup. In the Nameservers section, replace any default entries with ns1.yourbrand.in and ns2.yourbrand.in, tick the boxes to assign an IPv4 address to each if WHM prompts — accepting writes the matching A records into your domain's DNS zone — and Save. Resellers without full WHM are covered by the host's pre-configuration. Belt-and-braces: also create the ns1/ns2 A records inside the yourbrand.in DNS zone itself via the Zone Editor.

Step 4: pointing client domains

pointing client domains. Do this on one site or a staging copy first, then check the public URL in a private window so cache does not hide the result. Stop if the page errors, and email support@webji.services with the step name and the exact error before you repeat it on every account. WebJi® support mail is staffed 24/7 in Hindi and English; the phone line +91 141 4941811 is business hours only.

Testing propagation

Testing propagation properly, before declaring victory:

1. Check glue at the parent — dig NS yourbrand.in @a.gtld-servers.net (or the .in registry servers) should return your ns1/ns2.
2. Check A records — dig ns1.yourbrand.in from a public resolver, or whatsmydns.net for the visual global view.
3. Check a client domain — dig NS clientdomain.in from multiple networks, then dig clientdomain.in for the A record.
4. Grade the whole setup — intodns.com or an MXToolbox DNS report flags missing glue, lame delegation and zone mismatches.

Give it 48 hours before any verdict; glue can lag because registries cache host records longer than ordinary records. If a client domain still resolves old after 48 hours, verify their registrar actually saved the custom nameservers — the silent failure mode.