Hi @ryan. Any chance you could give this a nudge (ticket 1589737)?
It’s absolutely not something I’m expecting support to fix in this ticket for me but I do honestly think it is something you guys need to change at some point as it’s an unnecessary hurdle and something I honestly believe Cloudflare is doing incorrectly for no good reason (other than not enough thought went into the initial implementation).
I created a Feedback - Usage & Design post for what I think needs to happen:
and I’d be happy to at least know that somewhere in the organisation it’s recognised and put on a roadmap for review or something. It’s a trivial change (actually undoing some unnecessary Cloudflare record tweaking) and will fix something that’s clearly broken when it’s looked at properly and objectively.
EDIT: One other thing - if I have two domains (example.com and example.org, say) both proxied by Clouflare then I can set an SRV record on example.com which points to port 443 on exmple.org just fine! So this is nothing to do with you not allowing SRV to point to Cloudflare-proxied hostnames, it’s just the logic as to when records are converted is screwy.