DNS points to prohibited IP
The IP address is the one provided by the website host and so I am unsure what other A record could be created to avoid the issue
We’ve tried reviewing the IP address and the DNS records on both the domain host and cloudflare
Your domain is pointed to the Cloudflare IP address 172.66.0.70 while it should point to your origin server/web host.
Might be it’s automatically added or while you were adding your zone to your CF account, the scan added it.
Could you please re-check for the correct one and edit the particular DNS record?
If you don’t know the original records, then contact your web host to get the records to use to point to your site and enter those manually into the Cloudflare DNS.
Helpful article how to manage DNS records at Cloudflare dashboard:
Hi, thank you for response and help!
So it is my understanding that 172.66.0.70 is the origin server/web host. It is the IP address provided by the website hosting platform but maybe I am misunderstanding the terms?
Thank you!
The specified IP address is from Cloudflare network, which is why you see this 1000 error.
Yes, you need to obtain the IP address from your Web hosting provider and change it at Cloudflare DNS tab menu to point to the correct server IP. The web hosting platform should be able to provide it to you.
So this is what my web hosting platform has provided - this is where I have pulled the 172.66.0.70 from and then added the A record to the Cloudflare DNS record. But it is causing some conflict?
Could you temporary Pause Cloudflare, wait for 5mins and re-try again? 
Looks like your web hosting platform fetches the proxied 
Cloudflare IP instead of it’s own.
May I ask if you are using Hostinger, Bluehost, GoDaddy, WP Engine or?
I’m using IONOS for the domain host and then Carrrd for the website host.
I’ll give the pause a go!
Thank you
In the meantime, from the screenshot at the DNS tab of Cloudflare dashboard for your zone, you can safely remove the four NS type of the DNS records on the list (ns116, ns1118, ns1078).
From the DNS history, I could find the IP address co-related to the IONOS hosting. My best guess is this is the IP address to which you need to point your A type DNS record for hollyfirkins.com under the DNS tab of Cloudflare dashboard:
Could you please give it a try as well? Then if the Website would respond and work fine over the HTTPS, you can safely un-pause Cloudflare and make sure the DNS record(s) are proxied and that your SSL settings at Cloudflare dashboard are set to “Full (Strict)”.
Thank you again!
So I have removed the NS records. And changed the A type to point to IONOS.
Will wait and see if the site becomes accessible!
Now it seems to point to IONOS but it says it is not yet connected to a website?
Thank you!
Thank you for patience and feedback.
Strange that IONOS picked-up Cloudflare IP for A @ 172.66.0.70
Should be A @ 217.160.0.96 at IONOS, despite the Cloudflare DNS is now the “main one”.
At Cloudflare DNS tab, could you also switch the to 
(DNS-only) for the CNAME autodiscover and _domainconnect records (just in case)?
Not at all - thank you for all the amazing help!
If the IONOS DNS is inactive does it mean they are having no influence over the routing? Should I update the records regardless?
These records are now DNS only
Yes, since domain is using Cloudflare nameservers, then Cloudflare DNS is responsible.
Before proceeding to edit DNS records at IONOS dashboard, may I ask how did you activated your Cloudflare for your Website?
Since using IONOS; are you using IONOS so called “CDN” (if yes, then here we can check: Managing DNS Services - IONOS Help) which actually is some kind of a Cloudflare plan/package/service integrated within IONOS, and it might be correctly then to be pointed to the Cloudflare IP 172.xxx., but if true then we have to figure out and obviously use (DNS-only) for the hollyfirkins.com and CNAME www at Cloudflare dashboard since DNS records to cannot work in this kind of a setup.
Otherwise, you’ve used some 3rd-party service provider to activate Cloudflare?
Or you’ve done this manually for your domain/website?
Originally we didn’t set up Cloudflare knowingly. There was an error when trying to view our website and when contacting IONOS support they said it was a Cloudflare issue and to go through CF. Since then we registered for Cloudflare and have been trying to resolve different issues in setup
What I know from my experience with IONOS, I’ve had few websites and few servers there.
Once I’ve changed my domain nameservers to Cloudflare, I only had to point my DNS records to the IP address of these web hosting package/IONOS cPanel/servers.
Just in case, you can always reset the DNS at IONOS.
And after this step, we can compare and modify what’s needed at Cloudflare DNS tab to look the same as DNS records on IONOS interface.
Here is the article just in case we’d need it (since IONOS DNS has got @ A pointed to the Cloudflare already somehow which from my best guess is wrong and should be reset to default):
Furthermore, if the above doesn’t help and fix, then we can proceed with a step since you also still don’t have any records pointing to IONOS by A/AAAA/CNAME, we can ask IONOS support to provide you what those should be and add them to your both IONOS and Cloudflare DNS.
Thank you for feedback.
I do understand your frustration here with a simple “copy-paste” as it should be easy steps to setup your Website working with Cloudflare. Sometimes they occur, but we’re here to help.
Should I reset the name servers along with the DNS?
Wait a second, is this the service you’re using for hosting your Website?
