When you build a web design agency or a reseller hosting business, branding matters. If your clients log into their domains and see your upstream host’s default nameservers instead of your own brand, it immediately breaks the illusion of a fully independent service. Learning how to configure custom nameservers for white label hosting allows you to replace those generic host domains with professional, branded alternatives like ns1.yourdomain.com and ns2.yourdomain.com.
Achieving a fully white-label environment involves setting up private nameservers in your reseller control panel, registering those nameservers with your domain registrar, and ensuring your DNS zones point correctly. This guide walks you through the exact process using cPanel and Web Host Manager (WHM).
Understand Private Nameservers and How They Function
Before modifying records, it helps to understand what a private nameserver actually is. Every domain name requires authoritative nameservers to direct traffic across the internet. Standard domains rely on the nameservers provided by their web host or registrar. When you run a reseller or agency hosting business, you want those lookups to resolve through your own chosen domain name rather than a third-party corporate URL.
Creating private nameservers involves two distinct layers of configuration. First, you create glue records at your domain registrar. Glue records map your custom nameserver subdomains to specific server IP addresses. Without glue records, recursive resolvers would enter an infinite loop trying to resolve the IP address of a nameserver hosted on the very domain it is trying to look up Namesilo guide on glue records. Second, you configure the server software, such as cPanel and WHM, to accept incoming DNS requests for those specific nameservers.
1. Configure Your Initial Nameservers in WHM
To begin the server-side setup, log into your Web Host Manager dashboard using your root or reseller administrative credentials. Depending on whether you manage a dedicated server, a virtual private server, or a high-level reseller package, the exact menu path may vary slightly, but the core settings remain identical across environments.
Navigate to the basic setup area in your dashboard, often found by typing terms like basic into the sidebar search filter cPanel and WHM documentation. Look for the section designated for default nameservers. Here, you will define your primary and secondary hostnames, such as ns1.yourdomain.com and ns2.yourdomain.com. Assign the corresponding IP addresses provided by your hosting provider to each nameserver entry. Save these configurations before moving forward to ensure the server registers the changes in its underlying configuration files.
2. Register Glue Records at Your Domain Registrar
Once your server acknowledges your new custom nameserver hostnames, you must register them with the company where you purchased your primary domain. Log into your domain registrar control panel and locate the domain management tools for your brand domain.
Find the option for managing custom nameservers or glue records. Enter your nameserver subdomains along with their exact public IP addresses. This step tells the global root registry that your specific domain possesses authority to answer DNS queries. Skipping this registration step will cause DNS resolution failures for any client websites attempting to use your branded nameservers.
3. Update Reseller Nameservers and Client Defaults
If you operate a multi-tiered reseller account or manage multiple sub-resellers within your infrastructure, you need to enforce these branded nameservers across all newly provisioned accounts automatically.
Within WHM, locate the interface designed for editing reseller privileges and nameservers Edit Reseller Nameservers and Privileges. Select the appropriate username and assign your custom nameservers as the mandatory default. This ensures that every time you or your automation scripts spin up a fresh cPanel account, the system automatically populates the zone files with your branded nameservers instead of the root server defaults.
Troubleshooting Common DNS Propagation and Resolution Errors
Even with careful execution, DNS changes rarely take effect instantly across the entire globe. Because internet service providers, local routers, and recursive public resolvers cache DNS records to improve web browsing speeds, full propagation can take anywhere from a few hours up to an entire day.
If you encounter site loading errors or find that your custom nameservers fail to resolve, use command-line diagnostic tools like dig or nslookup to query authoritative root servers directly. Check that your A records match on both the server side and the registrar side. A single typo in an IP address will disrupt the entire handshake sequence and prevent visitors from reaching client websites.
How to Configure Custom Nameservers for White Label Hosting: Sources and Further Reading
- How to Set Up Nameservers in a cPanel & WHM Environment | cPanel & WHM Documentation
- Edit Reseller Nameservers and Privileges | cPanel & WHM Documentation
- How to Set Up Custom Nameservers (Glue Records) | Namesilo Blog
- Account custom nameservers · Cloudflare DNS docs
Frequently Asked Questions
Why Should I Use Custom Nameservers for White Label Hosting?
Using custom nameservers hides your underlying upstream provider from your clients. It helps build brand loyalty, establishes professional authority, and prevents clients from bypassing you to contact your datacenter directly.
What Is the Difference Between Setting Up Nameservers in WHM and at My Registrar?
Setting up nameservers in WHM provisions the server-side DNS rules and A records, while registering them at your domain registrar tells the global root DNS infrastructure that your domain acts as an authoritative nameserver.
How Long Does It Take for Custom Nameservers to Start Working After Configuration?
Global DNS propagation typically takes between 2 to 24 hours depending on your registrar and ISP caching, though local changes often resolve much faster.
