We’ve made some changes to a subdomain and noticed a very strange bug: if the domain is not proxied through Cloudflare it reaches our A record fine, however, as soon we turn proxing on, it reaches Zendesk instead of our servers as setup.
It appears this subdomain used to be used for Zendesk historically and despite being moved to another domain, it looks like they’ve used Cloudflare SaaS and the records have persisted (incorrectly) and is taking precedence over our own records/control on the domain itself.
Turning off proxying again does resolve this, but we need this for our use case.
Seems like two bugs:
Cloudflare: not giving us the ultimate control over our DNS - Even if we wanted to override Zendesk
Zendesk: not cleaning up their Cloudflare SaaS records when a domain is changed
Please see Twitter thread for more detail on this: