Skip to content

[Errors] Clarify CNAME record requirements and terminology #29116

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ngayerie wants to merge 1 commit into
base: production
Choose a base branch
from
Open

[Errors] Clarify CNAME record requirements and terminology #29116

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions ...support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1001.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,12 +14,16 @@ This error indicates a DNS resolution failure preventing access to the requested
- An external domain that is not on using Cloudflare has a CNAME record to a domain active on Cloudflare
- The target of the DNS CNAME record does not resolve.
- A CNAME record in your Cloudflare DNS app requires resolution via a DNS provider that is currently offline.
- [Always Online](/cache/how-to/always-online/) is enabled for a [Custom Hostname (Cloudflare for SaaS)](/cloudflare-for-platforms/cloudflare-for-saas/) domain.
- [Always Online](/cache/how-to/always-online/) is enabled for a [custom hostname (Cloudflare for SaaS)](/cloudflare-for-platforms/cloudflare-for-saas/) domain.
- An A record for a subdomain (`www.example.com`) points to the IP address of a [wildcard custom hostname (Cloudflare for SaaS)](/cloudflare-for-platforms/cloudflare-for-saas/) (`*.example.com`).

### Resolution

A non-Cloudflare domain cannot CNAME to a Cloudflare domain, unless the non-Cloudflare domain is added to a Cloudflare account.

Attempting to directly access DNS records used for [Cloudflare CNAME setups](/dns/zone-setups/partial-setup) also causes error 1001. For example, `www.example.com.cdn.cloudflare.net`.

Disable [Always Online](/cache/how-to/always-online/#enable-always-online), if using [Custom Hostname (Cloudflare for SaaS)](/cloudflare-for-platforms/cloudflare-for-saas/) domain.
Disable [Always Online](/cache/how-to/always-online/#enable-always-online), if using [custom hostname (Cloudflare for SaaS)](/cloudflare-for-platforms/cloudflare-for-saas/) domain.

Use a CNAME record for subdomains pointing to a wildcard custom hostname.
Please also note that [o2o](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/) only applies when the CNAME points to the target defined by the SaaS provider (`customers.saasprovider.com`), not to the [apex proxying IP](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/#prerequisites).
Loading