How do we block domains once apps incorporate their own DNS over HTTPS?
Inside the private network it was great because it could be detected and manipulated as necessary - redirecting rogue DNS queries to the desired DNS servers if specific software and apps were attempting to use their own hard-coded DNS servers (to bypass ad-blocking etc.), blocking unwanted domains and sites, etc.
Using Pi-Hole my current DNS request block percentage is 45.8%. I specifically redirect DNS requests through it using firewall rules. If I remove or disable the DNS redirection firewall rule this percentage falls to around 25 - 30%, meaning that there are a number of internal devices and software that are using specific, custom DNS servers rather than what my DHCP server hands out. I don't like that, but vanilla DNS lets me close that potential security hole.
What if these devices and software start using internal DNS over HTTPS (or any of the other forms of non-inspectable or non-specific-DNS-port DNS requests) settings that are non-configurable?
How do we even detect that it's occurring, never mind being able to manipulate it to comply with the 'policies' of our private networks?