Since pihole isn’t maintained anymore, i just installed adguard on a neat subdomain on my server.
It works but… some stuff don’t work. As i stated before about pihole : nothing is logged, no client is detected, no stats at all are recorded anywhere. But blocking works… I wonder if there is a fix to this, let’s ping @ericg who maintains it, and i’ll open an issue on github too.
Well after some more testing it appears adguard does not work at all. The domains that appeared blocked in my tests were just coincidentally unreachable, nothing i do to my network seems to do the trick…
What i don’t understant is that adguard suggest to use some_local_ip:54 as DNS server IP but neither the router nor the network resolver on my laptop accepts :54 at the end of the DNS address, and DNS request seem to usually use port 53, not 54. Anyone can clarify anything ?
I restored pihole which works out of the box, despite the logging and displaying problems that i stated here. It would be great if someone took back maintenance on pihole…
I worked hard on the AdGuard Home package to improve it for DNS over HTTP/TLS/QUIC usage
It’s a major rework of the package, it has been tested many many times so it should be fine, but I’m aksing for testers!
If you’re using DNS over HTTP/TLS/QUIC, your testing will be precious for me!
And even if you’re not using DNS over HTTP/TLS/QUIC, your test is very welcome!
So if you want to help me to release it quickly and that you’re willing to take a risk, you can test the package using this command:
Please tell me if everything is working properly, if you’ve found a bug, if the documentation isn’t clear, etc!
Tell me also if everything is perfect! ^w^
Thanks!
Edit: if you want to downgrade after testing, just uninstall adguardhome and restore the pre-upgrade backup