How to Set Up Custom (Vanity) Nameservers Correctly

Custom (vanity) nameservers let your domain use branded names like ns1.yourdomain.com instead of your host's — but they only work if you register glue records and create matching A records. Skip either step and the nameservers will not resolve. Here is the correct sequence.

What vanity nameservers are

Instead of pointing your domains at your host's nameservers, you use your own branded ones. This is common for resellers and hosting brands who want ns1.yourbrand.com and ns2.yourbrand.com to appear as the authoritative nameservers.

Step 1: Register glue at your registrar

Because the nameservers are inside your own domain, you must register glue records — associating ns1.yourdomain.com and ns2.yourdomain.com with the IPs of your DNS server. Use the registrar's "register a nameserver" / "host records" function. See registering private nameservers with VernalWeb.

Step 2: Create matching A records in your zone

In your domain's DNS zone, add A records for ns1 and ns2 pointing to the same IPs as the glue. The glue (at the registry) and the A records (in your zone) must agree.

Step 3: Configure the server side (WHM)

On a cPanel/WHM server, set up the nameservers and assign the IPs so the server answers authoritatively for them — related to setting custom nameservers in WHM. On Webuzo, the DNS/nameserver settings play the equivalent role.

Step 4: Point your domains at them

Update each domain to use ns1.yourdomain.com and ns2.yourdomain.com as its nameservers — see updating nameservers.

Step 5: Verify

Use dig +trace and query your new nameservers directly to confirm they answer authoritatively, and allow for propagation.

Frequently asked questions

Why do my vanity nameservers not work after I set them?

The most common cause is missing or mismatched glue. The registry must publish IPs for ns1/ns2.yourdomain.com, and your zone's A records must match. Without glue, the names cannot resolve at all.

Do I need two nameservers?

At least two is standard for redundancy, and many registries require it. Ideally they are on different IPs (and ideally different networks) so one failing does not take your DNS down.

How long until vanity nameservers take effect?

Registry and nameserver changes are subject to propagation, so allow time for caches to update. Verify directly against your new nameservers with dig while the wider internet catches up.