Issue with CNAME Cross-User Banned
I am having an issue with a CNAME record where it is setup to resolve to a site (secureframe.com) and it is being blocked. I can see that secureframe mentions that it is a block on the Cloudflare side: https://support.secureframe.com/hc/en-us/articles/22631334142995-Troubleshooting-DNS-issues-with-Trust-Center-custom-domains#h_01HFSESY[…]SCPQM5PNDN
I've already filled out the abuse form but is there anything else I can do to expedite a fix?
Secureframe Help Center
Troubleshooting DNS issues with Trust Center custom domains
SSL certificate issues
If you use CAA records to control who can issue SSL certificates on your domain, in order to use a Secureframe Trust custom domain, you must allow Google Domains to issue a c...
6 Replies
this is infact an issue that only secureframe can resolve
cloudflare blocks cnaming zones that aren't in your account
(https://community.cloudflare.com/t/setup-cname-to-using-another-cloudflare-zone/591755/3)
secureframe needs to enable cf4saas
but they say in their documentation that its a cloudflare issue
and they are wrong
they linked to this: https://community.cloudflare.com/t/error-1014-cname-cross-user-banned-how-to-resolve/324935
which has a resolution that says:
Resolution
To allow CNAME record resolution to a domain in a different Cloudflare account, the domain owner of the CNAME target must contact Cloudflare Support and specify the domains allowed to CNAME to their target domain. A Cloudflare Pro, Business, or Enterprise plan is required on the target domain for Cloudflare Support to change default CNAME restrictions.
so does that mean Secureframe since theyre the target?
They shouldn't link to that, it's wrong.
As @Idle mentioned, Secureframe need to configure your domain as a Custom Hostname in their account.
Thank you both @Laudian @Idle