dns-server-setup VS serverless-dns

Yes, looks like the code you're looking for lives in https://github.com/AhaDNS/dns-server-setup/blob/master/files/scripts/bash/unbound_update.sh

https://github.com/AhaDNS/dns-server-setup/blob/master/files/iptables/rules.v4 if interested

Doesn't really have to be a "mega" server, Aha DNS got a 4 core 8 gb machine in the Netherlands, and it comfortably handle 7 millions requests per day. But that's not a pi-hole instance because all it did is resolve everyone's request while blocking with oisd list.

Haha I know what you mean :) On the bright side it is open-source: https://github.com/AhaDNS/dns-server-setup

sky is a stub resolver, which after stripping out all request information, forwards the dns query to both Cloudflare and Google DoH servers (code), and replies from which ever responds back the fastest. Both the client app and the resolver (server) are open source, so if you find any leaks and know what's up, we're open to changes.

There is also https://github.com/serverless-dns/serverless-dns that works on user-configurable list combinations using Cloudflare Workers (100k queries per day), though it can't be integrated with WARP.

Max (fly.io) and Sky (cloudflare) are both are no logs. You can examine the code to ascertain this (here) and also check the version of the code we've deployed too (via github actions).

You can selfhost your own adblocking server on Cloudflare Workers and edit the upstream, you get Quad9 malware filtering, Cloudflare's nearest servers, and whatever blocking list you want.

Took us wayyy longer than originally planned, because not only personal life got in the way, we also run our own resolver (open source) maintaining which took away some of our time too. Especially, as the costs were mounting, we couldn't ignore it and had to optimize it as much as we could (which we since have).

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).

I swear this idea wasn't generated over chats and coffee with GPT3; though, most of the code for this feature was most certainly written by it (commit). Be careful with your reviews of this feature then; you don't want to upset a sentient Optimus Prime AI.

If you are deploying your own rdns, then logs and analytics are up and running (check the github readme). NRDs and other things will happen as we near launch (in a month or two, perhaps). But we are just 2 developers, and our time is really all spent on the Android app, and not the service...

Maybe, this is what you want? https://github.com/serverless-dns/serverless-dns