For Pi-hole, you'd have to find a block list or block the domain which may or may not block the entire service (I guess that the same might be true for AdGuard Home, however). This can be done on Pi-hole as well, but AdGuard gives you a list of these services and checking a box will block the entire service. I can see one specific benefit to AdGuard Home: if you have kids, it's very easy to block entire services (YouTube, Twitter, Facebook, etc.). I included my resolution in the Pi-hole tutorial I created, so there might not even be a setup difference if you follow both guides. YMMV though, as the issues I was running into were container specific DNS issues. I'm sure if I continue to use AdGuard Home, I would notice a few things that aren't being blocked but it has to be blocking 95%+ of normal ads in order for me to see no practical difference.Īs far as setup goes, AdGuard Home was significantly easier to setup, as I had major Docker container issues when initially setting up Pi-hole. However, that's probably an indirect praise to AdGuard Home, as I have a bunch of block lists that I added to Pi-hole and didn't add anything to AdGuard Home (only using default list). If I'm being honest, there has been no practical difference between the two as far as blocking ads. U/WunderTechTutorials - could you help point me in the right direction? Any help would be greatly appreciated.

My intuition is that it is something to do with the fact that AdGuard is running in a docker container that is not using the host or bridge network, but my knowledge of Docker is very limited. The DNS server sitting at 192.168.1.3 is configured correctly, because when I configure my router to use it, everything resolves correctly. Server '192.168.1.3': could not be used, please check that you've written it correctly however when I 'Test upstreams', I get an error: My 'Upstream DNS servers' configuration in AdGuard looks like this: To illustrate, my DNS server setup looks like like this:Īlso, since the DNS server is running on the same NAS, it is at 192.168.1.3:53 My setup is such that I also have a DNS server running on the same Synology NAS that routes all my of internal network URLs to the same IP that is running a reverse proxy. However I am stuck trying to get my internal routes to resolve. I was able to get it set up with your instructions.

Adguard synology