It’s a temporary feature until there’s a standard to replace it. Intimately DoH isn’t needed to make IoT transparent, an IoT device can establish a TLS tunnel

It’s a temporary feature until there’s a standard to replace it. Intimately DoH isn’t needed to make IoT transparent, an IoT device can establish a TLS tunnel to a CDN, and unless that’s blocked you have no way of knowing what is being sent where. An in-line https proxy is the only solution, if iot devices fail to check certificates (which wouldn’t surprise me) If they do check, and you can’t provide your our root, then you can’t trust them. Read GNU manifesto and realise why it’s important. I am conflicted over DoH. As an end user I want to be protected against rogue networks - especially in hotels. As a network admin I want to be protected against rogue end devices. As both I want to be able to deploy split dns servers due to Nat, not to force users (including me), but to don’t to them where to go. DoH should have been implemented at the OS level and driven by DHCP unless overridden, as with normal DNS.