Child Name Server is not a term with a consistent and well established meaning, so it is a little unclear what exactly you are hoping to accomplish.
If you are simply wanting to operate your own authoritative nameservers on your own hosts using your own domain name for use with other domains, all you need to do is create A records using the IPs of the hosts that house your nameservers. Add AAAA records if you want them to be accessible over IPv6. Ensure that those hostnames are set to DNS Only.
If you want use Cloudflare’s nameservers and have them respond to names in your domain, you need the feature that Cloudflare calls custom nameservers. This will require glue records if they will serve as the authoritative servers for their own parent zone.
If you are seeking to delegate a child zone to nameservers outside of Cloudflare, that follows a different process.
Yes I want to create my own authoritative nameservers. But problem is, when simply creating A Dns record pointing to ip address , those name server is not accepted by other domains’ registrars. I tried many of them. They simple reject those nameserver as they are not valid. So I feel like I need to upgrade account to paid ones? Because there is not other menu for creating custom nameservers.
If you want, I can write ones that I created. They are not usable…
Have you asked your registrar why they are not accepting your nameservers? That’s where you probably should start. Unless your nameserver hostnames are set to proxied, this should be unrelated to anything at Cloudflare.
What have you named your nameservers?
Can you share the name of a zone that they are currently serving?
I tried three registrar and they generate:
In-Zone nameservers not added at the registry: ns1.ns2ip.com,ns2.ns2ip.com (Resellerclub)
or
Nameservers are not valid
So this can not be at their side. This is probably at cloudflare side. And I really do not understand how “must have action” this is no possible.
Can you ask them please if you have a paid account Mine is free…
I do not think so. I also tried updating a domain at godaddy and got this:
We cannot save your changes that are not registered with this ad publisher. Verify that your listing is correct and check with the DNS provider this advertiser is registered with.
So resellerclub, godady and other two major domain registrar in Turkey does not accept them.
To recap, I registered a domain ns2ip.com at cloudflare and created two ns1 and ns2 A record. Am I missing something?
No man it is not about it. I deleted one record ns2.ns2ip.com still not accepting them.
As domain is registered at cloudflare. It it responsable for creating child nameserver to use on other domains. But there is not such option. All I can do is to create simple dns a record and they do not help.
Can you explain clearly what you are trying to do as none of what you have said makes sense?
If you want to create an external nameserver, you have to do that yourself. Cloudflare can merely point your subdomain at it using a DNS record as you have done (and seem to be doing).
Or are you trying to create a vanity nameserver as described here?
If so, do you have a Business or Enterprise plan? Such vanity nameservers can only be used for zones in your account.
I’ve dug deeper as your explanation isn’t clear, the internet isn’t clear on an answer either so I’ve dug deeper by using Godaddy with one of my test domains and pointing at yours, and various other nameservers of mine.
The message isn’t clear, so perhaps as the registrar themselves. This may be a glue issue, they may require the glue records for your domain to point at the nameservers you are creating. You could try to raise a ticket with Cloudflare to ask for this. It’s not something that would be done automatically.
That had crossed my mind as well, though it really should only be necessary when a nameserver needs to be authoritative for its parent zone.
You may not have created your request in the appropriate category. All plans can open account, billing, and registrar tickets. This would be a registrar support request, since your domain is registered with Cloudflare registrar, and the registrar is the party that needs to submit the glue records to the parent zone.
I thought the same as well, just may be overzealous checking. I tried Godaddy with my domain’s nameserver ns1.example.com (example.com registered on Cloudflare with ns1.example.com as an account vanity nameserver) and that was accepted (there is glue for that), but it refused to accept ns1.sub.example.com which are (zone) vanity nameservers for a subdomain setup (so the IPs for those won’t match the glue).