Cloudflare has done something very smart with its domain business.
It offers domain registration at essentially cost, which sounds like a fantastic deal. No big markup. No unnecessary upsells. A clean interface. And if you’re already using Cloudflare for DNS, CDN, security, and proxying, putting your domains there feels like the obvious choice.
But there is a catch that is easy to overlook:
When you register a domain through Cloudflare Registrar, you don’t just choose Cloudflare as your registrar. You are also committing the domain to Cloudflare’s authoritative nameservers.
Cloudflare’s own documentation is explicit: domains acquired through Cloudflare Registrar must use Cloudflare nameservers. If you want to use another DNS provider, you have to transfer the domain to another registrar. (Cloudflare Docs)
For a domain you intend to keep forever and use with Cloudflare indefinitely, maybe that’s perfectly acceptable.
For a business, however, I think it’s a poor trade.
You Are Saving Pennies and Giving Up Flexibility
The primary argument for Cloudflare Registrar is price.
And yes, paying essentially wholesale pricing is attractive.
But ask yourself what you’re actually saving.
A few dollars per year.
Now compare that with what you’re giving up: registrar independence.
With a conventional registrar, your domain registration and your DNS provider are separate decisions.
You can register a domain at one company and point its nameservers anywhere you want:
- Cloudflare
- Amazon Route 53
- DNS Made Easy
- your hosting provider
- a specialized DNS provider
- your own infrastructure
- a buyer’s infrastructure
The registrar holds the registration.
The DNS provider handles DNS.
Those are deliberately separate layers.
That’s a good thing.
Cloudflare Turns Those Layers Into One Dependency
Cloudflare Registrar collapses those decisions together.
Register the domain with Cloudflare and Cloudflare becomes the registrar and the mandatory authoritative DNS provider.
Cloudflare says this directly: all domains on Cloudflare Registrar use Cloudflare nameservers, and if you need different nameservers, you have to move the domain to another registrar. (Cloudflare Docs)
That may not sound important until you actually need to move something.
Suppose you sell the domain.
The buyer wants to use another DNS provider.
No problem, right?
Well, not quite.
You first have to transfer the domain away from Cloudflare before the buyer can use different authoritative nameservers.
That’s an unnecessary dependency in what should be a simple domain transaction.
Domains Are Assets. Keep the Control Plane Flexible.
This becomes even more important if you own a portfolio of domains.
A domain isn’t a website.
It isn’t a hosting account.
It isn’t a Cloudflare zone.
It is an Internet namespace that you may eventually point somewhere completely different.
That’s precisely why I prefer keeping the registrar layer independent from everything else.
Today, the domain might point to Cloudflare.
Tomorrow, it might point to:
A buyer’s servers.
Or:
A different CDN.
Or:
A different DNS provider.
Or:
A marketplace landing page.
Or:
Nothing at all.
The registrar shouldn’t dictate that decision.
Cloudflare Is Excellent at DNS. That’s the Point.
This isn’t an argument against Cloudflare.
Quite the opposite.
Cloudflare’s DNS infrastructure is excellent, and there is no reason you can’t use it.
You simply don’t need to register your domain there to use it.
Cloudflare itself explains that you can keep your domain at another registrar and simply change the authoritative nameservers to Cloudflare. (Cloudflare Docs)
That’s the architecture I prefer.
Registrar: Company A
DNS: Cloudflare
Hosting: Company B
Email: Company C
Website: WordPress (or other open source platform, not because they are free, but that is another article).
Each component can be changed independently.
That’s not unnecessary complexity.
That’s avoiding vendor lock-in.
“But Transferring Out Is Easy”
To be fair, Cloudflare doesn’t prevent you from transferring your domain out after a 60 day lock period.
You can unlock the domain, obtain the authorization code, and transfer it to another registrar. Cloudflare documents the process itself. (Cloudflare Docs)
But notice what that means.
If you discover that Cloudflare’s nameserver requirement doesn’t work for your particular project, the solution isn’t:
Change the nameservers.
The solution is:
Transfer the domain to another registrar.
That’s a much bigger operational event.
And domain transfers come with their own eligibility rules and potential delays.
Why create that dependency in the first place?
The Real Cost Isn’t the Registration Fee
This is the part I think gets lost in the Cloudflare Registrar pitch.
The question isn’t:
“Where can I register this domain for the lowest possible price?”
The better question is:
“What registrar gives me the most control over the asset?”
Saving a few dollars per year is easy to quantify.
The cost of being locked into a particular infrastructure arrangement is much harder to quantify — until you actually need to change it.
And that’s exactly when you don’t want to discover the limitation.
Keep Your Registrar Boring
I actually think the ideal registrar is somewhat boring.
It should:
- register the domain
- renew the domain
- let you change nameservers
- let you manage DNSSEC
- let you lock and unlock the domain
- provide transfer authorization codes
- give you straightforward domain management
That’s it.
Your registrar doesn’t need to be your CDN.
It doesn’t need to be your WAF.
It doesn’t need to host your website.
It doesn’t need to provide your analytics.
And it certainly doesn’t need to control where your authoritative DNS lives.
Use Cloudflare for the things Cloudflare is exceptionally good at.
Just don’t confuse excellent infrastructure with excellent domain ownership architecture.
The Few Dollars Aren’t Worth It
If Cloudflare Registrar were dramatically cheaper, perhaps the tradeoff would be interesting.
But the savings are generally small.
And the restriction is very real:
Cloudflare Registrar domains must remain on Cloudflare nameservers. (Cloudflare Docs)
For someone registering one personal domain and planning to use Cloudflare forever, I wouldn’t lose sleep over it.
For a business with important domains, a developer managing client properties, I would rather pay a few extra dollars and preserve the freedom to choose my DNS provider later.
Because the domain is the asset.
Cloudflare is infrastructure.
Keep the two separate.