The request reached Cloudflare, but Cloudflare could not work out which of its customers it is for: the domain is not active on Cloudflare, or it points at a Cloudflare domain with a CNAME Cloudflare will not follow.
Error 1001: DNS resolution error
| Error | Error 1001: DNS resolution error |
| Usually fixed by | The domain owner |
| Shown by | Cloudflare, instead of the site |
| Between | The DNS setup and Cloudflare — not the visitor |
Look up the domain’s DNS
Look up the domain’s records: see where the name points, and whether a CNAME leads to a Cloudflare domain.
What it means
Cloudflare answers for many domains on the same addresses and picks the customer from the name requested. Error 1001 means it could not: the name is not an active Cloudflare site, or it arrives through a CNAME from a domain outside Cloudflare that Cloudflare does not accept.
Why it happens
- A request for a domain that is not, or no longer, active on Cloudflare but still points at Cloudflare’s addresses.
- A domain not on Cloudflare with a CNAME to a domain that is.
- A CNAME whose target does not resolve, or whose DNS provider is offline.
- Visiting a partial (CNAME) setup target such as www.example.com.cdn.cloudflare.net directly.
How to fix it
- Check where the name points with the lookup above.
- If the domain should be on Cloudflare, make sure the zone is active in the Cloudflare account.
- A domain outside Cloudflare cannot CNAME to a Cloudflare domain unless it is added to a Cloudflare account; otherwise point it at the origin server directly.
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- Error 1001 — developers.cloudflare.com
- Cloudflare 1xxx errors — developers.cloudflare.com