DoH VS dohservers

Even those who weren't interested in self-hosting might spend a couple of minutes hosting their own DNS proxy since it's much more flexible and don't require root or dedicated port (at least with DoH).

To inject a little paranoia, DoH spec and implementation don't actually require the providers to only use /dns-query, it's possible (and very simple) to create an innocuous-looking website with /supersecretdns serving DoH, or directly on the homepage itself (the request for DoH vs regular webpage has different header), but if your kids are already that proficient, no way to stop them aside from plugging off the router.

Get a PHP hosting (dime a dozen these days), and proxying on PHP is also seamless, pretty much any website can have a secret URL that serves DoH.

https://github.com/NotMikeDEV/DoH/blob/master/dns.php handles both POST & GET. Yours only work with the POST, used by Chrome & Firefox, but not AdGuard.

If you are paranoid about a particular DNS server knowing your requests (but not paranoid enough to just use Tor entirely), the alternative will be just running a recursive resolver where you're running that PHP file. This exposes your server IP to the nameserver, but that's it, no extra third parties are involved. Or take it to the next level by running Tor there and forwarding plain DNS requests through it.

DoH can be somewhat protected with a secret path, you can even create one for free on Cloudflare Worker or any PHP hosting, but only Windows 11, iOS, macOS, and browsers support it natively. DoT is supported by Android natively but hiding the custom domain is more complex (you'll need wildcard cert, which requires manual record update with LetsEncrypt every 90 days), and if someone snoops on your traffic since they can see the domain for the DoT.

That relies on a list of known DoH providers. Private DoH server won't be in the list, which can be very easily made on any PHP hosting or even just a Cloudflare Worker.

shouldn't be that hard, just load one of these... https://github.com/Sekhan/TheGreatWall https://github.com/oneoffdallas/dohservers

No reason to put private IPs in public DNS. Use split DNS and block port 853 and use this list for DoH.

There is some meager effort like this, but it's seriously trivial for one to create their own DoH proxy, or heck, just create their own NextDNS config. So even if you block port 853 (used by DoT & DoQ) and port 53 (unencrypted DNS), DoH traffic is simply unstoppable, yes there is traffic analysis, but with DoH3 it would be impossible to detect an innocuous-looking website serving regular traffic has a hidden DoH endpoint.

I run Pfsense and am able to block most common DoH services. I’m sure you will be able to configure similar options on opnsense. The best way to do this is a DNS block through AGH and an IP block with opnsense. Firefox provides what domains to block to disable their DoH, https://support.mozilla.org/en-US/kb/configuring-networks-disable-dns-over-https. You can also add these two lists to block most other common DoH services, https://github.com/oneoffdallas/dohservers, https://github.com/Sekhan/TheGreatWall. These lists will work with AGH for DNS blocking and for IP blocking aliases. If you have any Apple devices on your network you can use these domains to block private relay, https://raw.githubusercontent.com/Rogacz/private-relay/main/pr2.txt. I recommend you add these private relay domains as a custom entry in AGH to return NXDOMAIN so that the device shows that private relay is unavailable versus using a NULL response where it will say it’s available when it really isn’t. With these lists added to DNS blocklists as well as IP blocklists I have seen almost no DoH services getting through. The only service that I’ve experienced getting through the rules so far is Next DNS since it uses different IPs depending on what is fastest for your location, making it harder to block. I found a way to discover the IPs for their servers near you and will edit the post if I find the instructions again. Also make sure to completely block port 853 to block DoT. Lastly using these instructions from Pfsense, you can redirect or block all DNS queries that aren’t destined for your AGH instance. The instructions should be transferable to opnsense.

I’ve also been using this to block doh domains: https://github.com/travisboss/TheGreatWall - and in conjunction, at router level, I block their IP endpoints: https://github.com/oneoffdallas/dohservers

DoH serves is another story of course. You can at least check https://github.com/oneoffdallas/dohservers/ It can be imported directly into Pi-Hole

After reading through this and looking at some other sources I think I am going to create a URL Table of IPs that updates every X days using the list from https://github.com/oneoffdallas/dohservers/blob/master/iplist.txt . And I'll add in the few Cloudflares that it has commented out. And I'll use that alias to block outgoing 443 to those IPs. It seems pretty low maintenance and I don't have to have another package installed, which I was hoping to avoid. And I'll block all outgoing 853 as well. We'll see how it goes

Step 5: Add the DNS over HTTPS lists to your pihole (https://github.com/oneoffdallas/dohservers)

This isn't a complete approach, but you can block outgoing traffic from hitting DoH servers. https://raw.githubusercontent.com/Sekhan/TheGreatWall/master/TheGreatWall_ipv4 https://github.com/oneoffdallas/dohservers