Yes and no. The problem is different - the problem is application vs OS DNS resolvers. It's not an application job to be a DNS client, this is what actually su

Yes and no. The problem is different - the problem is application vs OS DNS resolvers. It's not an application job to be a DNS client, this is what actually subverts system administrator policies. Just as if some application has a hardcoded DNS (over UDP) address, but worse because there's encryption and authentication involved, so the system administrator cannot enforce the policy (sans patching the binary or hooking it at runtime). But if DNS over HTTPS is implemented at the system resolver level there is no issue (and the actual transport doesn't matter).