DNS points to prohibited IP - Godaddy wordpress

What is the name of the domain?

avclub.ro

What is the error number?

Error 1000

What is the error message?

DNS points to prohibited IP, Ray ID: 8b3fcca2af550d89 •

What is the issue you’re encountering

I had two websites (managed Wordpress on GoDaddy)and Cloudflare as DNS provider.

What steps have you taken to resolve the issue?

Both websites have been working fine for 6 months and just today they stopped working with
this error. What step could I take? Perhaps using a different CDN/DNS provider than Cloudflare. Why did Cloudflare became so unreliable?

What are the steps to reproduce the issue?

go to https://avclub.ro

Screenshot of the error

1 Like

I’ve disabled the proxy on Cloudflare and I still get the same error. This is beyond ridiculous.
You’ve requested a page on a website (avclub.ro) that is on the Cloudflare network. Unfortunately, it is resolving to an IP address that is creating a conflict within Cloudflare’s system. Why did this happen all of the sudden if I’ve been using this IP (Godaddy’s IP ) for several months. Can’t Cloudflare give a warning that it doesn’t like Godaddy’s IPs at least.

From my end, “www” is redirecting to the naked domain, and the naked domain is showing your website just fine.

Are you still seeing any issues?

If so, - where exactly (what IPv(4|6) addresses) are you pointing DNS record(s) to?

https://dash.cloudflare.com/?to=/:account/:zone/dns/records

After disabling the proxy and waiting for a while (15 minutes) it started working fine. So clearly Cloudflare doesn’t like Godaddy IP address. Any idea why is that ? The IP address is 160.153.138.10
Obviously I have no reason to enable the proxy again so unless Cloudflare clarifies why the IP from GoDaddy is forbidden I have to think about using a different CDN/proxy.

The IP address is in a Godaddy ASN, but if the request is going to Cloudflare (see http://160.153.138.10/) it may be that Godaddy is doing something with Cloudflare here now as a few people have reported the same over the last few days.

This came up before where IP addresses shown on WHOIS to be in a Godaddy AS were being announced by Cloudflare’s AS209242 so they were anycast. That’s not the case here but maybe something has changed/is changing for the affected IP ranges.

[add] When I checked this I was using Warp. It seems inside Cloudflare, Cloudflare thinks this IP range is owned by Cloudflare. Outside, requests go to Godaddy as expected.

1 Like

Hi all,
Unfortunately, we are also experiencing the same issue detailed by @mihai1
Similarly, our WordPress pages are hosted on GoDaddy and we were alerted to Error 1000.

Over recent weeks we have changed nothing on Cloudflare or GoDaddy, everything was working fine. A customer’s email notified us of the issue in the last hour.

Our DNS A record is also Proxied and we are hesitant to turn off the proxy of the A Record, because Cloudflare support page states it allows Cloudflare to protect our traffic:

"All proxied records will return Cloudflare IP addresses - This allows us to protect your traffic and to ensure for expected behavior

The IP addresses shown publicly will receive requests for your domain and then we will use the corresponding IP address or CNAME record(s) you have entered in our DNS control panel to proxy requests to your origin server"

Is there any further update on this?

removed proxy and it worked

We are also facing the same issue. Disabling the proxy resolved the issue for the time being. But this is not a proper solution. I contacted Godaddy support and after one hour of investigation, they said something went wrong on Cloudflare’s side. But the Cloudflare support team also doesn’t help with this technical issue. So, I guess we are kind of stuck in a loop. Hope it will be resolved soon.

Hello,

We have been rolling out a fix for this issue. Can you please re-test and let us know the issue you are still seeing please.

We appreciate your patience with this matter.

2 Likes

To ensure our sites were accessible over the last few days, we also had to turn the proxy off for the 3 DNS records:
A our_domain_name.com
CNAME *
CNAME www

We have tunrned back on the proxy for those DNS records and everything seems to be fine again.
Thank you @eportillo and Team! :+1:
Al

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.