At any domain registrar i could make my own nameserver record, why here i can’t which is a basic job for domain owner
If Cloudflare is the registrar, then you must use Cloudflare for DNS. It’s in their conditions.
1 Like
I will use it, i need to create nameserver to use for other domains to link them to my vps
Is there any solution or workaround for this?
Simply add the desired ns1, ns2, ns3, […] A and AAAA record(s) within your DNS settings, pointing towards the actual IP address(es) of your name servers.
It is as simple as that.
2 Likes
I wish it is that simple, ns must be registered to be able to use them as ns, not A, AAA records only
It really is.
“For other domains” in your phrase is the key here.
When you have your domain example.org, and that domain is served by the two name servers john.ns.cloudflare.com and jane.ns.cloudflare.com, all Cloudflare need to do is to add the relevant A/AAAA records for john.ns.cloudflare.com and jane.ns.cloudflare.com as mentioned above.
At the parent registry for example.org, you then just add that you wish to use the john.ns.cloudflare.com and jane.ns.cloudflare.com name servers for that domain .
The same applies to your example, where your indications make it sound like you have example.org, that you currently have with Cloudflare (e.g. through the john.ns.cloudflare.com and jane.ns.cloudflare.com name servers) and wants your friends / customers to be be able to indicate ns1.example.org, ns2.example.org, and ns3.example.org as the name servers for their domain names.
You simply just do the same, with the A / AAAA records alone, in your DNS of example.org, and nothing more.
Your friends / customers then point their domain to ns1.example.org, ns2.example.org, and ns3.example.org through domain registrar / registry.
There is really nothing more than that.
If example.org would need to be served by name servers named ns1.example.org, ns2.example.org, and ns3.example.org, you would need to register GLUE records in the parent registry for example.org and indicate it’s IP addresses there( too), but that one only applies when the name server is supposed to be the name server for it’s own parent domain.
Your indications are however that you would be using Cloudflare, but only use the name servers for other domain names, as such, the actual need of GLUE records / “registration of name servers” (except from the typical A / AAAA records) will fall apart.
So no, they must not be registered, with the actual case / situation you explained.
i tried this already but the registrar of the other domains report this error
“name servers error, please check and try again”
after contacting the customer service, they said that and ns has to be registered first as nameserver at the domain registrar before being used and they give me this tool to validate the ns record
https://webwhois.verisign.com/webwhois-ui/index.jsp?language=en_US
if the nameserver is registered it return data , else if i made only A record it not return any data, and they don’t accept it as ns in their control panel
-
Mind sharing what exact domain registrar that the above doesn’t work with?
-
And the domain TLD (e.g. com/net/org/[…]) that is currently held on this registrar?
-
As well as the TLD (e.g. com/net/org/[…]) for the domain on Cloudflare, that is supposed to hold the name servers?
I’ve seen quite a few things in my time, including domain registrars with quite defective systems.
I’m just starting to wonder, if the registrar you use for that other domain might be one of them…
The registrar
dynadot.com
I’ve multible domains there,
Forsankuwait.com
I can’t change the name server to
ns-de-001.host-cube.com
ns-de-002.host-cube.com
BTW, as a little side note, … running “all” your name servers on multiple IP addresses on the exact same machine, or even with different machines, but within the exact same network is a failure.
The Internet Standards, e.g. RFC2182 / Best Current Practice #16, requires a minimum 2 name servers, but preferably 3 - 7, where at least one of them MUST be completely separated from the others.
The above attempt doesn’t qualify for that, as both hostnames go towards IP address within the same provider.
$ dig SOA forsankuwait.com @ns-de-001.host-cube.com
; <<>> DiG 9.18.9 <<>> SOA forsankuwait.com @ns-de-001.host-cube.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 35500
$ dig SOA forsankuwait.com @ns-de-002.host-cube.com
; <<>> DiG 9.18.9 <<>> SOA forsankuwait.com @ns-de-002.host-cube.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 37445
status: REFUSED indicate that those two name servers are NOT configured to respond to DNS queries for that domain.
I would therefore start by making sure that your name servers actually respond properly for the domain you try to change the name servers of, and then try again on Dynadot.
Yeas, i removed the domain from the server that’s why dns not respond now, when i could not add the name server, the Dynadot told me that they can’t accept name server as A record only and i should register it as name server before using as nameserver (and they give me steps at their site to do this) , and that is where i stacked, here in Cloudflare i can’t register as nameserver
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.