Ever wanted your domain to use custom nameservers like ns1.yourdomain.com instead of generic ones like ns1.cloudns.net? That's DNS branding—also called vanity nameservers or white-label DNS—and it usually costs money. But here's the thing: you can actually set it up for free with ClouDNS if you know the right steps.
Most DNS providers lock this feature behind premium plans. ClouDNS officially lists DNS branding as a paid feature on their pricing page. But there's a workaround that lets you configure your own branded nameservers without spending a dime. This guide walks you through the entire process, step by step.
Before diving in, make sure you have these two things ready:
A domain where you can add child nameservers. Most domain registrars call this "Child Name Servers," "Glue Records," or "Private Nameservers." If you're not sure whether your registrar supports this, just reach out to their support team—they'll point you in the right direction.
A ClouDNS account with "Free (Legacy 2018)" status. This is the key ingredient. Legacy free accounts from 2018 have different capabilities than newer free accounts. If you registered with ClouDNS a while back, check your account type in the dashboard. New free accounts might not work with this method, though it's worth trying if you already have one.
If you're looking for a reliable DNS management solution that supports advanced features like this, 👉 getting started with a DNS provider that offers flexible configuration options can make a huge difference in how you manage your domains.
Start by creating a new DNS zone in your ClouDNS dashboard. Click "Add New" and then select "Master Zone." Keep all the default settings and enter your domain name. For this example, let's say you're setting up example.com.
Once you click "CREATE," ClouDNS will generate the initial DNS records for your domain, including default NS (nameserver) records pointing to their infrastructure.
Now comes the important part. You need to add A records that point your custom nameserver hostnames to ClouDNS's actual server IP addresses.
First, find the IP addresses of your assigned ClouDNS nameservers. These appear in the bottom right section of your ClouDNS dashboard. They'll look something like ns101.cloudns.net with an IPv4 address next to it. Important: The actual IP addresses vary by account, so you must use the ones shown in your specific dashboard.
Let's say your dashboard shows:
ns101.cloudns.net → 185.136.96.100
ns102.cloudns.net → 185.136.97.100
Now create A records for your custom nameservers. If you want to use ns1.example.com and ns2.example.com, add these records:
ns1.example.com → 185.136.96.100
ns2.example.com → 185.136.97.100
Click "Add new record" in your DNS zone, select "A" as the record type, and fill in the hostname and IP address. Repeat this for each nameserver you want to create.
You can actually name these anything you want—dns1.example.com and dns2.example.com work just as well, or even something creative. Just make sure you create at least two nameservers since most registrars require a minimum of two.
Here's where it gets a bit circular, but stick with me. Before you can register your custom nameservers with your domain registrar, those nameservers need to actually resolve to valid IP addresses. But they won't resolve until your domain's DNS is being served by ClouDNS.
So temporarily update your domain's nameservers at your registrar to point to the default ClouDNS nameservers (like ns101.cloudns.net and ns102.cloudns.net). This makes your A records from Step 2 go live.
After updating, wait for DNS propagation to complete. This typically takes anywhere from one hour to 24 hours, depending on various factors. 👉 Managing DNS changes efficiently becomes easier once you understand propagation timing.
Once propagation is complete and your custom nameservers are resolving properly, you can register them as child nameservers (glue records) with your domain registrar.
The exact process varies by registrar. Look for settings labeled "Child Name Servers," "Glue Records," "Private Nameservers," or similar. You'll need to enter both the hostname and IP address for each nameserver—the same information you added to your DNS zone in Step 2.
For example:
Nameserver: ns1.example.com → IP: 185.136.96.100
Nameserver: ns2.example.com → IP: 185.136.97.100
Before moving forward, verify that your custom nameservers are responding correctly. You can ping them from your command line or use online DNS tools to check that they're returning the correct IP addresses.
Now that your custom nameservers are registered and working, update your domain's nameserver settings at your registrar one final time. Change them from the default ClouDNS nameservers to your new custom ones:
ns1.example.com
ns2.example.com
This is the step where everything comes together. Your domain now uses your own branded nameservers while still being powered by ClouDNS infrastructure behind the scenes.
The final step is updating the NS records inside your ClouDNS DNS zone to reflect your custom nameservers. Go back to your ClouDNS dashboard, open the DNS zone for your domain, and look for the existing NS records (they'll still point to ns101.cloudns.net and similar).
Click the edit icon next to each NS record and change them to your custom nameservers. So instead of:
ns101.cloudns.net
ns102.cloudns.net
You'll have:
ns1.example.com
ns2.example.com
Save your changes. After DNS propagation completes (give it up to 24 hours to be safe), your DNS branding setup is complete.
You can confirm everything is working by using online DNS checking tools. Visit a site like dns.computer and enter your domain. It should show your custom nameservers responding correctly to DNS queries.
Your domain now has professional, branded nameservers while benefiting from ClouDNS's reliable infrastructure. Pretty neat for a free setup, right?
This method specifically works with ClouDNS "Free (Legacy 2018)" accounts. If you have a newer free account, the process might work differently or may not be available at all. It's worth testing, but don't be surprised if you encounter limitations.
Also, remember that all IP addresses mentioned in examples are placeholders. Always use the actual IP addresses shown in your specific ClouDNS dashboard—they're unique to your account's assigned nameserver location.
If you run into issues at any step, double-check that you've followed the sequence exactly. The order matters because each step builds on the previous one. And if something still isn't working after 24 hours, reach out to ClouDNS support or your domain registrar's support team for assistance.
With your custom DNS branding in place, your domain setup looks more professional and gives you better control over how your DNS infrastructure is presented to the world.