A DNS record on Cloudflare points at an address Cloudflare will not connect to — usually one of Cloudflare’s own addresses, or a reverse proxy that sends the request straight back through Cloudflare. The record needs your origin server’s real IP address.
Error 1000: DNS points to prohibited IP
| Error | Error 1000: DNS points to prohibited IP |
| Usually fixed by | The domain owner |
| Shown by | Cloudflare, instead of the site |
| Related | Error 1002, DNS points to Prohibited IP / Restricted |
Look up the domain’s DNS
Look up the name’s A records: a Cloudflare address there, when the record is proxied, is the loop.
What it means
A proxied record should hold the address of your own server. When it holds one of Cloudflare’s addresses, or leads through another proxy back into Cloudflare, the request would go round in a circle, so Cloudflare stops it.
Why it happens
- An A record set to a Cloudflare IP address — often copied from a lookup of the proxied site itself.
- An A or CNAME record pointing at another reverse proxy that forwards the request back through Cloudflare.
- A record pointing at a SaaS provider on Cloudflare that has not set up your custom hostname.
How to fix it
- Ask your host for the origin server’s IP address and put that in the A record.
- Replace a looping reverse proxy with a redirect at the origin.
- For a SaaS provider, ask them to configure your custom hostname — the error comes from their account.
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- Error 1000 — developers.cloudflare.com
- Error 1002 — developers.cloudflare.com