Creating custom nameserver and glue record

Being new to using Cloudflare as my registrar, I was wondering how to manage the domain settings like you would at other registrars. For example, if I decide in the future that I want to run my own name servers, where would you specify the glue record for the domain? This would basically mean that for this domain, it would only use CF as a registrar and not use any of their other services.

On the DNS page for the zone, it has a button for creating custom name servers, however, this appears to be for making the name server on CF and not making your own that would be hosted locally. If it is, then why would someone choose to use CF as their registrar when every other registrar allows you to set the name servers and glue records for free?

Custom nameservers are currently only possible with at least a business plan.

Yeah, but they’re talking about pure Registrar settings…which are still a work in progress.

1 Like

a) Currently :wink:
b) I somehow doubt Cloudflare would open that, otherwise they lose one business incentive, but then maybe they will at some point

1 Like

I’m not sure if you completely understand registering a nameserver in this context, but there is no negative impact to Cloudflare.

If I own example.com, and want other sites such as customer.example to use my name servers, I need to not only create a/aaaa records for ns1.example.com/ns2.example.com but I also need to register those nameservers so that there is appropriate glue records available to the TLD roots.

This is completely separate from Cloudflare’s custom nameserver feature (which could allow Cloudflare itself to host said nameservers).

@thedaveCA, Correct. I’m just wondering if the capability will be there to use a private name server for the root domain and add the glue record so it knows ns1/2.example.com’s IP. The custom nameserver offered by Cloudflare seems to me to be Cloudflare’s server and not your own.

Adding Hosting Nameservers NS Records on the DNS app is very similar to this topic but only answers the ability to use a subdomain as a name server and not the root.

1 Like

Glue is only necessary if you want to use hosts as nameservers which belong to the same domain for which you want to define these nameservers. The moment you use these hosts for another domain glue becomes irrelevant as regular DNS mechanisms will apply. Check out https://tools.ietf.org/html/rfc7719#section-6

And this would be the very definition of Cloudflare’s custom nameserver support.

But TLDs sometimes require nameserver registration if you want to use e.g. ns1.example.com in another .com domain (or a domain in an operationally related TLD, like .net or .edu*). DNS doesn’t technically require it, but it can improve efficiency, and TLD policy sometimes does require it regardless.

* Those examples should stop being true soon.

Fair enough, for such cases yes.

This support doc helped me. I’m on the free tier and added a glue record for my domain. It’s just an A record for your domain like so:

A example.com 1.1.1.1

That support doc is for Business and Enterprise plans where you can have custom name servers. Free tier doesn’t support this.

In Business plan there is an option to create name server. But if you are using Cloudflare as registrar you can not use those custom name server. There is no option to assign glue record.

I will always point to XXX.ns.Cloudflare.com not ns1.domain.com

In theory, as far as I know from experience (I have custom NS with CF Registrar) they should update automatically. If they don’t contact support and they’ll fix that for you.

Matteo,

you must have custom name server before you transfer your domain to Cloudflare. Cloudflare team doesn’t help in custom name server when they are the registrar. No option to set custom name server.

I had them before, but I changed them while I was with the CF Registrar. They changed them for me.

Unfortunately can’t test for you… contact them.

1 Like

Just a Cloudflare support staff reply.

1 Like

Cloudflare registrar is cheap and all but basically used as a loss leader and feeder to their business/enterprise plans.

From a business ethics/practices stand point, it is would be nice if they were explicit about this. It is a bit annoying to search around their (otherwise excellent) help and documentation and take ages to find this out.