Resellers want their customers to see their brand, including nameservers like ns1.theirbrand.com. On a master reseller plan you can give each reseller their own nameserver names, all pointing to the same server.
Before you start
- A VIP Master Reseller plan (see getting started with WHMReseller).
- The reseller's domain, registered at a registrar that allows creating child nameservers (glue records).
- The server's nameserver IP addresses from your welcome email or support.
How it works
Branded nameservers are just extra names for the server's real nameserver IPs. The registrar of the reseller's domain stores glue records (ns1/ns2 with IPs), and the reseller's domain zone has matching A records. Customer domains can then use ns1.theirbrand.com and ns2.theirbrand.com.
Create the glue records
- The reseller (or you) logs in at the registrar of
theirbrand.com. - Find Child Nameservers, Register Nameservers or Glue Records.
- Create
ns1.theirbrand.comandns2.theirbrand.comwith the server's nameserver IPs.
Add A records in the zone
In WHM Zone Manager, open the zone for theirbrand.com and add A records for ns1 and ns2 with the same IPs. The general process is also described in private nameservers.
Set the reseller's nameservers in WHM
- Open WHMReseller or WHM → Resellers → Reseller Center for the reseller (whichever your version uses for nameserver settings).
- Enter
ns1.theirbrand.comandns2.theirbrand.comas their nameservers and save. - New accounts the reseller creates get zones with these NS records.
Note: Existing zones keep their old NS records. Update them in Zone Manager, or ask support about a bulk update, if older accounts should show the new names.
Test
dig +short ns1.theirbrand.com
dig NS customerdomain.com +shortThe first should return the server's IP; the second shows the nameservers a customer domain uses after they update it at their registrar.
What the reseller tells customers
"Set your domain's nameservers to ns1.theirbrand.com and ns2.theirbrand.com." Include it in their welcome email (see welcome email template).
Troubleshooting
Registrar refuses the nameserver
The glue record must exist before customers can use the name. Create it under the reseller's own domain first.
Domains do not resolve
Check that the customer's zone exists on the server and propagation has finished.
Frequently asked questions
Do branded nameservers need separate servers?
No. They are names for the same nameserver IPs, so every reseller can have their own brand at no extra cost.
Can resellers set this up themselves?
They can create glue records at their registrar and add A records in their own DNS zone; setting reseller nameserver defaults may need your help as master reseller.
Do I need different IPs per reseller?
No. The same IPs work for every branded name.
How long do glue records take to work?
Usually minutes to a few hours, depending on the registrar and the TLD registry.