Error Code 1000 DNS points to prohibited IP

Cloudflare Error 1000 ("DNS points to prohibited IP") occurs when a site's DNS records incorrectly point to a Cloudflare IP address instead of the actual origin web server, creating a redirection loop. To fix it, update your A or CNAME records in the Cloudflare dashboard to point to your server’s real IP address, not a Cloudflare IP. 

Cloudflare Community +4

• Identify Correct IP: Obtain your actual hosting server's IP address from your web host.
• Update DNS Records: Log into your Cloudflare account, navigate to the DNS tab, and edit the A/AAAA records to use your server IP.
• Check CNAME Records: Ensure any CNAME records are not pointing to a domain that redirects back to Cloudflare.
• Disable Proxy (If Necessary): If you are using another service that also uses Cloudflare, you might need to set the record to "DNS Only" (grey cloud) to prevent a double-proxy loop.
• Purge Cache: Once updated, purge your Cloudflare cache. 
  Cloudflare Docs +4

• Misconfigured DNS: An A record points to a Cloudflare IP address rather than the origin server.
• Nested Proxies: The origin server runs a reverse proxy (e.g., Nginx) that points back to Cloudflare.
• Wrong IP: The site was migrated or changed hosts, but the old IP address was a Cloudflare IP.

Good Day!

There are several reasons why your IP may be resolving to Cloudflare, especially if you have an old website created under SiteBuilder.

To fix the issue, we need to update the DNS records inside your Cloudflare dashboard.

Steps:

• Identify Correct IP: Obtain your actual hosting server’s IP address from your web host.
• Update DNS Records: Log into your Cloudflare account, navigate to the DNS tab, and edit the A/AAAA records to use your server IP.
• Check CNAME Records: Ensure any CNAME records are not pointing to a domain that redirects back to Cloudflare.
• Disable Proxy (If Necessary): If you are using another service that also uses Cloudflare, set the record to “DNS Only” (grey cloud) to prevent a double‑proxy loop.

Alternatively, you may simply drop the domain name in question here in my comment, and I will check what is going on.