Cloudflare Error 1014: CNAME Cross-User Banned
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.
Status
Error 1014: CNAME Cross-User BannedExample
GET / HTTP/1.1
Host: custom.myclientsite.com
User-Agent: Mozilla/5.0
Accept: text/htmlHTTP/1.1 409 Conflict
Server: cloudflare
CF-RAY: 7d8e9f0a1b2c3456-ARN
Content-Type: text/html
<!doctype html>
<html>
<head>
<title>custom.myclientsite.com | Error 1014</title>
</head>
<body>
<h1>Error 1014: CNAME cross-user banned</h1>
<p>This domain is attempting to use a CNAME that points to a different Cloudflare account. The target account must authorize this connection.</p>
</body>
</html>How to Troubleshoot
Contact the CNAME target's owner
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.
Check your DNS configuration
Verify your CNAME record and what it points to. If the target is behind Cloudflare, cross-user authorization is required.
Check DNS RecordsUse a direct A record instead
If 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.
Target account: Set up Cloudflare for SaaS
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.
Common Causes
CNAME points to another Cloudflare account's domain
highYour 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.
SaaS provider has not configured Custom Hostnames
highYou are using a SaaS platform that runs behind Cloudflare, but they have not added your custom domain to their Cloudflare for SaaS configuration.
Moved domain to Cloudflare with existing CNAME
mediumAfter moving your domain's nameservers to Cloudflare, a CNAME that previously worked now fails because both sides are on Cloudflare.
Quick Diagnostics
Related Error Codes
Origin DNS Error
Cloudflare cannot resolve the origin server's DNS — typically shown alongside HTTP error 530.
DNS Resolution Error
Cloudflare's DNS could not resolve the requested hostname.
Origin DNS Error
A 530 error is returned alongside a 1016 error when Cloudflare cannot resolve the origin server's DNS.
Frequently Asked Questions
This reference was compiled from official RFCs, protocol specifications, and hands-on troubleshooting experience. AI tools were used primarily for formatting and organizing the content on the page.