DoH VS libcurl

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.

Then, in another terminal window, we use curl to hit the endpoint:

Made a PR to curl in line with the above: https://github.com/curl/curl/pull/13338

Through the Fast Forward program, we give free services and support to open source projects and the nonprofits that support them. We support many of the world’s top programming languages (like Python, Rust, Ruby, and the wonderful Scratch), foundational technologies (cURL, the Linux kernel, Kubernetes, OpenStreetMap), and projects that make the internet better and more fun for everyone (Inkscape, Mastodon, Electronic Frontier Foundation, Terms of Service; Didn’t Read).

From the GitHub Issue itself, the maintainer did end up creating a PR to fix a related issue: https://github.com/curl/curl/issues/12983

Also, the bot filed another issue despite the complaints.

This Docker image is designed to support implementing Github Actions with Python. As of version 4.0.0., it starts with the official python docker image as the base which is a Debian OS. It specifically uses python:3-slim to keep the image size down for faster loading of Github Actions that use pyaction. On top of the base, we've installed curl gpg, git, and the GitHub CLI. We added curl and gpg because they are needed to install the GitHub CLI, and they may come in handy anyway (especially curl) when implementing a GitHub Action.