dnsproxy-config VS FTL

Yes.

You can find the project here, the documentation describes installation alongside or in front of Pi-hole, depending on the use case. If you want secure incoming traffic, a certified FQDN is required. This is left as an exercise for the user (to raise the bar somewhat).

No need for the full AGH stack. You can easily run dnsproxy alongside or in front of Pi-hole.

I have somewhat documented the process of putting up a Do(H|T|Q)/DNScrypt proxy as a standalone service here.

I still need to fix up a couple of permission issues in my documentation, but I have the rough outline of deploying dnsproxy as a standalone simple service here. The last few edits I made to it were getting it to use the yaml syntaxed config file, and trying to make sure a default configuration should Just Work without having to edit it, but you'd still want to.

There's a basic overview here, but I haven't touched it for a while and the documentation may be slightly broken surrounding exec permissions on some files.

It's very possible. You could easily set this up yourself. I do so so myself using dnsproxy, and you could too.

I have an example dnsproxy service here that I use for high availability (one-to-many) distribution and providing encrypted transport.

You might know me as that Unbound guy, or maybe even that dnsproxy guy. Today I would like to make myself known as that Munin guy, and introduce munin-pihole-plugins for Munin Monitoring.

Kinda.

It's actually the name of the Pi-hole DNS server (FTLDNS) - pihole-FTL: - https://docs.pi-hole.net/ftldns/ - https://github.com/pi-hole/FTL

FTL v5.23

[✓] Detected ARMv8 (or newer) processor [i] Checking for existing FTL binary... [i] Downloading and Installing FTL...curl: (28) Failed to connect to github.com port 443: Die Wartezeit für die Verbindung ist abgelaufen [✗] Downloading and Installing FTL Error: URL https://github.com/pi-hole/ftl/releases/latest/download/pihole-FTL-armv8-linux-gnueabihf not found [✗] FTL Engine not installed

You will need to install it manually. You can find older versions on github: https://github.com/pi-hole/FTL/releases

To fix this, the "Other" category was introduced on this pull request: https://github.com/pi-hole/FTL/pull/1284.

FTL v5.22

curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the web page mentioned above. [✗] Downloading and Installing FTL Error: URL https://github.com/pi-hole/ftl/releases/latest/download/pihole-FTL-linux-x86_64 not found [✗] FTL Engine not installed Unable to complete update, please contact Pi-hole Support

Error: URL https://github.com/pi-hole/ftl/releases/latest/download/pihole-FTL-armv7-linux-gnueabihf not found