Custom nameservers (also called vanity nameservers) let your domain use nameserver hostnames on your own domain, such as ns1.yourdomain.com and ns2.yourdomain.com, instead of the default nameservers your host provides. They point to the exact same DNS service, just under your own brand.
What Custom Nameservers Are
Normally, a domain's DNS is managed through nameservers named after the host, something like ns1.example-host.com. Custom nameservers let you replace those with hostnames under your own domain instead. The DNS records and zone still live on the same servers behind the scenes: only the name your visitors and other systems see changes.
Why You Might Want Them
- You resell hosting and want clients to see your brand in their nameserver settings, not your upstream provider's.
- You run several related domains and want them all to reference nameservers on one primary domain for consistency.
- You simply prefer a cleaner, branded look when a client or partner checks your domain's DNS setup.
If none of this applies to you, you don't need custom nameservers. The default nameservers on your account work exactly the same and need no extra setup.
What You Need First: Glue Records
Before a domain will accept a nameserver hostname that lives on itself (or on a related domain pointing back to the same infrastructure), the domain registry needs a glue record. A glue record is simply the IP address tied directly to that nameserver hostname at the registry level, so other systems can find it without running into a circular lookup (your domain's DNS can't resolve ns1.yourdomain.com if the only place that hostname is defined is inside the DNS it's supposed to be serving).
If you skip this step, you'll typically see an error like "nameserver does not exist" or "host has no glue" when you try to set the custom nameservers on your domain. Get the glue record registered first.
How to Set Up Custom Nameservers
- Decide on the hostnames you want to use, for example ns1.yourdomain.com and ns2.yourdomain.com.
- Find the IP addresses of the nameservers you're pointing to. If you're using your hosting provider's existing nameservers, ask their support team for the IP address behind each one, since this is what the glue record needs.
- Register the glue records (sometimes called "child nameservers" or "host records") for your domain. This is normally done through your domain registrar's control panel, under a section like Nameservers or Host Records, where you'll enter the hostname and its matching IP address for each nameserver.
- Once the glue records are confirmed, go back to your domain's nameserver settings and set the domain to use your new custom hostnames instead of the defaults.
- Save your changes.
This process happens at the domain and registry level, not inside cPanel or DirectAdmin, so the steps are the same regardless of which control panel your hosting account uses.
Changes to nameservers can take up to 24-48 hours to fully propagate. Your site and email may be briefly affected while the change spreads across the internet, so it's best to make this change during a low-traffic period.
Common Issues
- "Nameserver does not exist" error: the glue record hasn't been registered yet, or hasn't propagated. Wait and confirm the glue record was saved correctly before retrying.
- Site goes down after switching: double-check the IP address in the glue record exactly matches the nameserver you intended to use. A typo here will send DNS lookups nowhere.
- Need to update the IP later: if the underlying nameserver's IP address ever changes, you'll need to update the glue record to match, or the custom nameserver will stop resolving correctly.
If you're not sure whether you need custom nameservers at all, or just want to check what nameservers your domain is currently using, see What Is a Nameserver and Why Does It Matter? first.