Cloudflare Error 1001: DNS Resolution Error

What’s actually happening

Like 1016, the Cloudflare error page shows, so traffic hit the edge — but here the issue is that the requested hostname isn't backed by a live Cloudflare zone. Most often you find an external domain CNAME'd onto a Cloudflare-hosted domain that was moved, deleted, or never properly added as an active zone. The domain may have worked before and broken when the underlying zone was removed. Removing the dangling CNAME makes it disappear.

Common causes

• External (non-Cloudflare) domain has a CNAME pointing at a Cloudflare domain it isn't authorized to alias
• The target Cloudflare zone was deleted or is no longer active in any account
• CNAME target doesn't resolve at all (dead external hostname)
• CNAME chain passes through a DNS provider that's currently offline
• Always Online enabled on a Cloudflare-for-SaaS custom hostname that no longer resolves

How to fix it

1. Find the dangling CNAMEdig example.com — if it's a CNAME to something.cloudflare-hosted.com, check whether that target is still a live, active Cloudflare zone. A CNAME onto a deleted zone is the textbook 1001.
2. Add the domain as an active Cloudflare zone (or stop pointing at one)A non-Cloudflare domain can't just CNAME onto a Cloudflare domain — add it to a Cloudflare account as its own active zone, or repoint the CNAME at a target that actually resolves.
3. Don't request the internal CNAME target directlyDNS records used purely as Cloudflare CNAME plumbing aren't meant to be hit head-on. Access the real public hostname instead.
4. For Cloudflare for SaaS custom hostnamesIf Always Online is on for a custom hostname, disable it; serving cached content for a hostname that no longer resolves triggers 1001. Confirm the custom hostname status is Active.
5. Confirm recoveryAfter fixing the zone or CNAME, dig example.com @1.1.1.1 should resolve to a Cloudflare edge IP and load. If it still 1001s, the target zone is likely still missing or inactive.