Question
Why did my subdomain's CNAME record fail to propagate with Cloudflare?
Answer
This is often due to the CNAME status being set to the default orange cloud icon. Switching it to the gray cloud option should resolve the issue.
The orange cloud icon in the screenshot is Cloudflare's default setting:
Click the orange cloud icon to change it to gray:
After this adjustment, it will take some time to propagate. This time can vary due to Cloudflare's system and your TTL value.
To confirm if your subdomain's CNAME record has propagated, visit the MxToolbox page: CNAME Lookup.
7 Comments
This answer is also frustrating because in order to use Page Rules at Cloudflare the CNAME has to be proxied. (the orange cloud). This is how to setup 301 redirects for example
Just disabling Cloudflare proxy is not a solution. We use Cloudflare for redirects too. Please either provide a redirect functionality or at least fix this bug, so that the Cloudflare proxy works for Zendesk, as for every other website on the net.
Btw, this used to work properly several months ago.
Any update here? Really disappointed I can’t use my own subdomain.
I am experiencing the same issue.
I had set up a cname with our subdomain and it seemed to work until just last week when Cloudflare has decided we are forbidden!
What do I need to resolve this issue?
Hi Narek Torosyan and Zendesk team,
Do we have a way to resolve the issue with proxied enabled on Cloudflare's CNAME with Zendesk?
Thanks
Hi Toan,
This may need more time to review and investigate. Would you mind reaching out to our Support team so we can assist you further? Thanks!
Please sign in to leave a comment.