Full of self-doubt getting my Rule to work. I had an old rule in place and it used to work fine (when I was proxing to you). I’d since changed to point the DNS to elsewhere, and when I moved it back to proxying through you, the Rule no longer works.
I have an almost identical Rule set up for the naked domain and it works fine. Have also deleted and recreated the rules and the dns entry.
@ → A record (192.0.2.1) + proxying
blog → A record (192.0.2.1) + proxying
That’s actually the conclusion I was starting to reach so I’m already talking to them about it. Definitely a little disconcerting to discover that they had any control of my DNS without me knowing it and that there’s no indication of that anywhere. That does also explain how my site ended up hosed while I was on holiday when they said it wouldn’t. Hey-ho.
Will update in here once I confirm and then close this off.
I removed the domain on the Kinsta side and the rules started working as expected.
I’m trying to get to the bottom of it because I don’t want there to be a situation where there is an invisible integration that they still have control over.
So far I’ve had fairly unsatisfactory responses from the team at Kinsta regarding what their integration with CF looks like (they’re saying that they don’t control anything in my CF account). There is a verification step where we needed to add a Kinsta specific key to our domain for the “integration” initially, but I’m not sure who was verifying what in that case.
I don’t suppose you know anything else about the nature of the integration?
Technically, that’s correct. Using Kinsta essentially cedes control to their account. For now. I now Cloudflare is working on O2O (Orange to Orange), meaning if you a hostname that ultimately points to a proxied server, that you’ll have some settings control, such as Page Rules.
a hostname that ultimately points to a proxied server, that you’ll have some settings control, such as Page Rules.