Getting "CNAME Cross-User Banned" using Cloudflare for Saas and r2 with custom domain. We have: 1. r
Getting "CNAME Cross-User Banned" using Cloudflare for Saas and r2 with custom domain.
We have:
The fetch above fails with "CNAME Cross-User Banned" Error 1014
BUT if we change fetch onto
Everything is OK.
I think that its a bug, as both domains are on same account, we are using cloudflare for SaaS, and access to
Important detail, the fail is reproduced ONLY if customer domain is placed on cloudflare.
And has
So our customer with
Has DNS entry on Cloudflare
No issues with disabled Proxy flag, no issues with providers like Namecheap, only if customer provider is Cloudflare itself
We have:
- r2 bucket with 2 custom domains https://developers.cloudflare.com/r2/buckets/public-buckets/#custom-domains-configuration
assets.webstudio.isandassets.wstd.work - Worker as SaaS fallback origin https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/domain-support/worker-as-origin/ with dispatch namespace inside placed on route
*/*atwstd.workzone - Worker route service for
assets.wstd.work/*is set toNoneto bypass2. - DNS Entries for SaaS with
proxy-fallback A 192.0.2.1*.customers CNAME proxy-fallback.wstd.work
The fetch above fails with "CNAME Cross-User Banned" Error 1014
BUT if we change fetch onto
Everything is OK.
I think that its a bug, as both domains are on same account, we are using cloudflare for SaaS, and access to
assets.wstd.work must not be preventedImportant detail, the fail is reproduced ONLY if customer domain is placed on cloudflare.
And has
PROXY enabled on route.So our customer with
poke-method.work domainHas DNS entry on Cloudflare
poke-method.work CNAME customer-id.customers.wstd.work with Proxy flag enabled No issues with disabled Proxy flag, no issues with providers like Namecheap, only if customer provider is Cloudflare itself