Error 1014 occurs when a domain has a DNS CNAME record that points to a hostname in a different Cloudflare account, and the target account has not explicitly allowed this cross-account CNAME resolution. Cloudflare blocks this to prevent unauthorized domains from riding on another account's Cloudflare configuration, SSL certificates, and security settings. This commonly happens with SaaS platforms and custom domain setups where the CNAME target is behind Cloudflare.
Your domain has a CNAME record pointing to a hostname that is proxied through a different Cloudflare account, and that account has not set up Cloudflare for SaaS (Custom Hostnames) to authorize your domain.
You are using a SaaS platform that runs behind Cloudflare, but they have not added your custom domain to their Cloudflare for SaaS configuration.
After moving your domain's nameservers to Cloudflare, a CNAME that previously worked now fails because both sides are on Cloudflare.
Ask the owner of the domain your CNAME points to (usually a SaaS provider) to add your domain as a Custom Hostname in their Cloudflare for SaaS setup.
Verify your CNAME record and what it points to. If the target is behind Cloudflare, cross-user authorization is required.
Check DNS RecordsIf the target provides a direct IP address, switch from a CNAME to an A record pointing to their origin IP. This bypasses the cross-user restriction but requires a static IP.
The Cloudflare account that owns the target domain needs to enable Cloudflare for SaaS and add the incoming domain as a Custom Hostname under SSL/TLS > Custom Hostnames.
Cloudflare cannot resolve the origin server's DNS — typically shown alongside HTTP error 530.
Cloudflare's DNS could not resolve the requested hostname.
A 530 error is returned alongside a 1016 error when Cloudflare cannot resolve the origin server's DNS.