This is an expected response to the client privacy vs network control arms race that escalated with the rise of DNS over HTTPS. Without picking a side in that

This is an expected response to the client privacy vs network control arms race that escalated with the rise of DNS over HTTPS. Without picking a side in that fight, I’m not sure this solution totally solves the problem when shared IP infrastructure is in play. A CDN may use the same IP for a malicious website and a perfectly good one, and the only difference is the incoming hostname being requested. The result is you annoy dns over https users, but in the end do not gain any control.