How to Fix Cloudflare Error 1001 (DNS Resolution Error)
What Error 1001 means
Error 1001 is Cloudflare's way of saying "I know this domain, but I don't know where it goes." When a visitor types your address, the request reaches Cloudflare because your domain's nameservers point there. Cloudflare then looks inside your DNS zone for a record — an A record pointing at a server IP, or a CNAME pointing at another hostname — that matches the exact address requested. If that record does not exist, there is nothing to forward the request to, and Cloudflare shows the 1001 page instead.
That is what separates a 1001 from the other Cloudflare 1xxx errors: a 1000 means the DNS points at a prohibited IP, a 1016 means the record points to a CNAME that cannot be resolved, while a 1001 simply means the record is absent. It is one of the most owner-fixable errors in the whole Cloudflare catalog, because the fix is usually a single DNS record — but visitors cannot do anything about it, since the DNS zone belongs to the site.
Common causes
- Missing DNS record: the hostname has no A, AAAA, or CNAME record in the Cloudflare zone — the single most common cause of a 1001.
- Record deleted by accident: a cleanup, a migration, or a well-meaning team member removed the record and the error appeared immediately after.
- www vs root mix-up: the zone has a record for example.com but not www.example.com (or vice versa), so only one version of the address works.
- Domain moved between Cloudflare accounts: re-adding a domain to a different account creates an empty zone — every record must be recreated.
- Nameservers no longer point to Cloudflare: zone edits do nothing if the registrar moved the domain to different nameservers; the lookups never reach Cloudflare.
How to fix Error 1001 — step by step
Step 1 is for visitors. Steps 2 through 6 are for site owners.
- Visitor: confirm it is a DNS problem, not your network. Load the site over mobile data instead of Wi-Fi, and try it in a second browser. If Error 1001 appears everywhere, the domain's DNS really is broken — no amount of clearing your cache or restarting your router will help, because the missing record is on the site's side. Skip to the alternatives below and let the owner know.
- Site owner: open the Cloudflare DNS zone and look for the hostname. Log in to Cloudflare, select the domain, then go to DNS, then Records. Search for the exact hostname showing the 1001 — remember that example.com and www.example.com are separate records. If the hostname is not listed at all, you have found the problem: Cloudflare is answering for the domain but has no record telling it where to send the traffic.
- Site owner: add the missing A or CNAME record. Click Add record. For a server with a fixed IP, choose type A and paste the server's IPv4 address; for a hostname managed elsewhere (a host's alias or a CDN target), choose CNAME and paste the target hostname exactly. Type the name field precisely — www for www.example.com, @ for the root, or the full subdomain. Copy the values from your hosting account rather than typing them from memory.
- Site owner: check for typos and the proxy setting. Read the record back character by character: one wrong letter in the name or target sends the error to the wrong place. Make sure the hostname you added is the one visitors actually type — if www.example.com works but example.com shows the 1001, you still need a root record. Leave the proxy status orange-clouded (proxied) unless you have a reason to bypass Cloudflare; grey-clouded records still need to exist, just unprotected.
- Site owner: confirm the domain is still using Cloudflare nameservers. Check the domain at your registrar: its nameservers must be the two Cloudflare nameservers assigned to this zone. If someone moved the domain to new nameservers, Cloudflare never receives the lookups and the zone edits in the previous steps do nothing. If the nameservers changed, either point them back to Cloudflare or manage the DNS at the new provider instead.
- Site owner: wait out propagation and verify with a DNS checker. New Cloudflare records usually work within a minute or two, but cached negative lookups can linger. Flush your local DNS cache, then test the hostname on an independent DNS checker such as dnschecker.org — if most locations resolve to your record, you are done. If the 1001 persists past a few hours, recheck the record for typos, confirm you edited the right Cloudflare account and zone, and purge the Cloudflare cache under Caching, then Configuration, then Purge Everything.
Did this fix it? Quick checklist
- The hostname loads in a private window with no 1001 page
- DNS → Records shows a record for the exact failing hostname
- Both the root and www versions of the address resolve
- The domain still uses the Cloudflare nameservers
If you are a visitor and the 1001 persists for a day or more, the owner's DNS fix is stuck — try the site's app, its social pages, or a web-cache copy in the meantime, and report the error to the owner through whatever contact channel you have. If you are an owner and records keep going missing, audit who has access to the DNS zone and turn on Cloudflare's audit log: deleted records usually trace back to a cleanup script, an expired integration, or a second account that also claims the domain.
Frequently asked questions
What does Cloudflare Error 1001 mean?
Error 1001 means Cloudflare received a request for your domain but could not resolve its DNS — there is no A, AAAA, or CNAME record for the requested hostname in your Cloudflare DNS zone. Cloudflare knows the domain but has no instructions for where to send the traffic, so it shows the 1001 page.
Can I fix Error 1001 as a visitor?
No — the missing DNS record belongs to the site, so only the site owner can add it. As a visitor you can confirm it is a real DNS failure by testing another network, then use an alternative route (the site's app, its social pages, or a cached copy) and tell the owner the site is down.
How long does Error 1001 take to clear after adding the record?
Usually a minute or two after the record is added in Cloudflare. If it lingers, stale negative DNS caches are the cause — flush your local cache and test again, and allow up to a few hours for resolvers worldwide to pick up the change. A 1001 that never clears means the record is still wrong or in the wrong zone.
Why does the root domain work but www shows Error 1001?
Because example.com and www.example.com are separate DNS records, and the zone only contains one of them. Add a second record for the missing hostname — a CNAME for www pointing at the root is the usual fix — and the 1001 on that hostname disappears.