The first time this has happened, we have hundreds of domains in our account. I cannot add the domain: stgeorgevets.com.au. It shows up in the registrar as purchased and completed with a few weeks since registration.
All I get is that it cannot be added as “stgeorgevets.com.au is
not a registered domain”.
Doing a WHOIS here validates the purchase:
Whois Lookup Captcha.
Any ideas why or how to determine the issue?
Did you get this working? It’s showing Cloudflare name servers.
The CF nameservers are added via the domain registrar. But I cannot add the domain to the control panel.
If you’re talking about the control panel here, you’ve skipped a step. You can’t set name servers at your domain registrar until
after they’ve been assigned to that domain by Cloudflare. Please set those name servers back to what you had before.
The domain registrar at time of purchase has been automatically assigning the CF nameservers (based on a domain template), and then we add the domain to CF.
We never had an issue and possibly done hundreds of domains in the past this way.
Is this a change?
Is this a change?
No, it’s always been a bad idea to set name servers at a registrar before the DNS host has assigned them.
Best practice is to have functioning DNS before you add a domain to Cloudflare. Even if that functioning DNS is a parked domain page, or just placeholder “A” records of 192.0.2.1
Ok I will give it a go, and revert.
Even after changing the nameservers and trying again, it has the same issue. It seems that CF is failing to recognise the domain.
It seems the name servers may have not yet fully propagated. I would suggest waiting at least a few hours and then trying again
I have left this for 10+ days, and still it is not letting me add the domain. It is not a propagation issue.
Please open a support ticket and post the ticket # here. You can open a ticket via email to
support AT cloudflare DOT com
Shoot, while the name servers seem to have propagated, there are no DNS records for that website.
I’ll escalate if this next tip doesn’t work:
Add an “A” record for
stgeorgevets.com.au and another for
www both with the IP address of 192.0.2.1 (just a placeholder IP address). Cloudflare really works best if there’s a functioning site, but IP addresses are usually enough to jumpstart it.
This is a brand new domain, there is no website (as yet). We are deploying it to run email services for the short term, hence no A records or any other DNS are in place.
We were wanting to have CF manage the DNS with hundreds of other domains we run on it.
The registrar I have bought the domain from charges a year in advance for hosting if I enable zone management, so to do this, I will need to cough up just under $200. Not sure what to do.
They provide name servers that don’t do anything?
I’d hate to have you jump through one more hoop, but
dns.he.net can set up fully functioning DNS for free. You’d be able to add those “A” records there.
Ok, no worries,
I have now setup the domain with another DNS service provider with some legit records, we will wait for propagation and then review in a couple of days.
I took it to the domain registrar who reckons that he checked the domain and it was ok. He couldn’t get it to connect to the DNS on my end, but then could on his end.
I have since tried it again and now it connects. So I think he must have done something backend, but I am none the wiser as to what.
In any case, Cloudflare is accepting this domain now and I can close this thread.
Thank you for your help.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.