There was however a small issue: the IP of the client machine was not showing up! AdGuard Home Docker container not showing the client IPs

I recently tried running an AdGuard Home Docker container and with no surprise, it worked perfectly after setting the NAS IP as the DNS server in my router, all my local DNS requests were sent to AdGuard Home and I could see it doing its job of blocking any known advertisement or tracking hosts. It’s a great NAS, but it’s the extra features like being able to easily run Docker containers that makes me like it even more!

There are already plenty of really good guides available for this so i’m not going to make another one, instead i’m going to point you to this guide which i think sums up the steps required very succinctly.I have a DS412+ Synology NAS that’s been running continuously for a few years now! Pi-hole is really easy to setup on a Synology NAS using Docker, and i would highly recommend you check it out for yourself. It even protects devices like your TV, which otherwise wouldn’t have any defence against ads. The most significant benefit of using Pi-hole is that it protects all your connected devices at the network level, and negates the need to have ad-blockers installed on each individual device. Once setup with some ad-lists, you simply redirect all DNS queries on your home router to the internal IP address of the Pi-hole, Pi-hole then passes any DNS queries it receives to the upstream DNS servers which you specify (Adguard DNS, Cloudflare, QUAD9, Google etc), and then filters the response against the specified ad-lists. You specify which domains to block via lists, which are freely available and generally fall into specific categories such as tracking, malware, ads etc. Pi-hole is a DNS sinkhole, it blocks adverts and tracking sites at a domain level, and works across your entire network to protect all your devices. This is by far one of the most useful things i have installed on my Synology.

Adguard home synology