Error 1000 DNS Points to prohibited IP - when connected to workers

[ace8]

I have no DNS records in Cloudflare for xxx.com.au domain. It is only connected to Workers and I have added the custom domain to workers yet I get IP conflict issues?

Error 1000

Ray ID: 751948946d00a86a • 2022-09-28 03:10:00 UTC

DNS points to prohibited IP

What happened?

You’ve requested a page on a website (xxx.com.au) that is on the Cloudflare network. Unfortunately, it is resolving to an IP address that is creating a conflict within Cloudflare’s system.

What can I do?

If you are the owner of this website:
you should login to Cloudflare and change the DNS A records for xxx.com.au to resolve to a different IP address.

[fritex]

Greetings,

Thank you for asking.

@ace8

I have no DNS records in Cloudflare for xxx.com.au domain. It is only connected to Workers

The error is correct as far as I am afraid your are putting Cloudflare IP instead of your hosting / origin server IP address into the Content field for both A and AAAA records.

You should get provided the IP address(es) from your hosting provider.

However, since using Workers on a defined route path like domain.com/*, may I ask if you’ve tried pointing to a temporary IP address for that particular proxied hostname (naked domain and/or www) like 192.0.2.1?

• https://support.cloudflare.com/hc/en-us/articles/360029779472-Troubleshooting-Cloudflare-1XXX-errors#error1000

Regarding Cloudflare 1000 error, I’d suggest you to into below articles for further troubleshooting and more information about the issue:

Fixing Error 1000 - DNS points to prohibited IP

General Information about Error 1000 This tutorial covers Error 1000 - DNS points to prohibited IP, which looks like this: [image] This error is most commonly caused due to one or more DNS records in the Cloudflare dashboard pointing to a Cloudflare IP address. It can also be caused if your DNS record(s) reference another reverse proxy. In this tutorial, we will focus on fixing the most common cause, DNS records pointing to Cloudflare IPs. If you see this error, follow the steps below and do…

Sharing helpful articles with step-by-step instructions how to manage the DNS records at DNS tab on Cloudflare dashboard as follows:

• https://support.cloudflare.com/hc/en-us/articles/360019093151-Managing-DNS-records-in-Cloudflare

Adding DNS Records

This tutorial covers adding general DNS records and specifically A, AAAA, CNAME, MX and TXT records. Go to the DNS app of your Cloudflare dashboard. Enter your credentials and click ‘Log In’ Click the domain in question Click [image] [Please note, the content of the records below are solely for example purposes and should be replaced by valid records with content provided by your web host] Please select which record you need help adding:

A Record

<a class="lightbox" href=&quot…

Editing DNS Records

This tutorial covers editing DNS records. Go to the DNS app of your Cloudflare dashboard. Enter your credentials and click ‘Log In’ Click the domain in question On this page, you will see a list of the DNS records for your domain. This page is where you edit them. You will see the list of records like this: [DNS Page] You can click the edit button to the right of any record to change it, then click ‘save’ when you’re done. There is also a tutorial on Adding DNS Records Tutorial Refer…

[ace8]

Hi @fritex thanks for reaching out with awesome helpful info. The issue was resolved in the end by modifying the CF Worker script. There was issues in the script and modified it see here: Using Cloudflare workers to redirect multiple URLS - Developers / Workers - Cloudflare Community

But as FYI you can indeed use CF workers without needing any A or CNAME records specified. You can add them direct to the Worker itself (To do so you must remove any A or CNAME records for the domain first then add them directly into CF workers) see screen shot and i have marked out confidential client data. hope this helps you as well.