Cloudflare Error 1001: DNS Resolution Error (Causes and Fixes)

Error 1001 is a DNS resolution error. Cloudflare received a request it could not map to a working hostname, so it returned a Cloudflare-branded page headed "DNS resolution error" with error code 1001 and a Ray ID. The site's server was never contacted.

Cloudflare's documentation lists four situations that produce it. All of them come from DNS configuration, so the fix is almost always in a DNS panel, not on the web server. Visitors cannot fix it; site owners usually can in a few minutes.

What triggers a 1001

Per Cloudflare's troubleshooting page, the common causes are:

1. A web request was sent to a Cloudflare IP address for a domain that does not exist on Cloudflare.
2. A domain that does not use Cloudflare has a CNAME record pointing at a domain that is active on Cloudflare.
3. The target of a CNAME record does not resolve.
4. A CNAME record in your Cloudflare DNS depends on a DNS provider that is currently offline.

Cloudflare also notes that visiting the internal DNS names used for CNAME setups directly triggers 1001. Its example is a name shaped like www.example.com.cdn.cloudflare.net. If you or a monitoring script request that name, you will see this error even though nothing is broken.

If you are a visitor

You cannot repair someone else's DNS. Try these quick checks, then report it:

• Reload after a minute. If the owner just changed DNS, the error can be transient.
• Check the address you typed. A typo in the domain, or a link to a stale subdomain, can land on a Cloudflare address that has no matching zone.
• Try another network or public resolver to rule out a local DNS cache.
• Tell the site owner you saw "Error 1001" and include the Ray ID from the page.

Use Is it down for everyone or just me? if you are unsure whether the problem is on your side.

If you are the site owner

Step 1: identify which cause applies

Ask two questions. Is the failing hostname inside a zone you have added to Cloudflare? And does it have a CNAME?

dig +short CNAME www.example.com
dig +short CNAME www.example.com @1.1.1.1
dig +short NS example.com

The DNS चेकर shows the same records from several locations, and the नेमसर्वर लुकअप tells you whether the domain delegates to Cloudflare at all. If the domain does not use Cloudflare nameservers but a CNAME points at a hostname that is a Cloudflare customer's zone, you have cause 2.

Step 2: a non-Cloudflare domain CNAMEs to a Cloudflare domain

Cloudflare's guidance is direct: a domain not on Cloudflare cannot use a CNAME to point to a domain that is on Cloudflare, unless the first domain is also added to a Cloudflare account. Your options are:

• Add the pointing domain to your Cloudflare account and move its nameservers.
• Replace the CNAME with an A or AAAA record that points at the real destination.
• If the target belongs to someone else, ask them whether they offer a supported custom-domain method (Cloudflare for SaaS or a similar feature) instead of a bare CNAME.

Step 3: the CNAME target does not resolve

Follow the chain. Every hop must end in an A or AAAA record:

dig +trace www.example.com CNAME
dig +short A target.example.net

An empty answer means the target name was deleted, misspelled, or lives in a zone that expired. Fix the target or point the CNAME somewhere valid. Stale CNAMEs pointing at decommissioned services are also a takeover risk; see subdomain takeover and dangling DNS and run the Dangling DNS Checker.

Step 4: a DNS provider is offline

If a CNAME depends on a name hosted at another DNS provider, an outage there breaks resolution through Cloudflare. Check that provider's status page, and consider whether a long dependency chain is worth it. Where you can, point records at IP addresses you control.

Step 5: stop requesting the internal names

If your logs show requests to *.cdn.cloudflare.net style names, find the script, monitor, or integration issuing them and switch it to your real public hostname.

After you fix it

DNS caches hold the old answer until the TTL expires, so allow time. See how long DNS propagation takes और TTL explained. Confirm with the Cloudflare एरर चेकर. If you changed records recently, DNS इतिहास can show what the zone looked like before the break.

Related errors

अगले कदम

• Check the live error code with the Cloudflare एरर चेकर.
• Inspect records with the DNS चेकर.
• Read Cloudflare DNS and SSL modes.
• Review DNS explained for website owners.

सामान्य प्रश्न

Is error 1001 a problem with my web server?

No. It is raised before any origin connection, from DNS records, so restarting your server will not help.

Why do I see 1001 on a name ending in cdn.cloudflare.net?

Cloudflare says that accessing those internal CNAME-setup names directly causes the error. Use your public hostname instead.

Can I CNAME a domain I do not manage on Cloudflare?

Not to a Cloudflare-hosted domain unless your own domain is added to a Cloudflare account. Use an A or AAAA record or a supported custom-hostname feature.

Does 1001 mean my domain expired?

Not directly, but an expired zone can make a CNAME target stop resolving, which is one documented cause. Check registration with the WHOIS लुकअप.

यह पेज सामान्य जानकारी है, जिसे हमारी संपादकीय टीम ने लिखा है और दस्तावेज़ीकरण बदलने पर अपडेट किया जाता है। सर्वर और प्रदाता अलग-अलग होते हैं, इसलिए बदलाव पहले सुरक्षित तरीके से जाँचें। देखें: संपादकीय नीति और अस्वीकरण.