Block Ads on Your Synology NAS with AdGuard Home in Minutes (2 Easy Ways!)

if you want to block annoying ads from showing up when browsing the internet you'll want to consider deploying Edgard home and in this video I'll go over two simple ways to set things up in just a few minutes on your sonology Nas If you're new to Edgard home it is a free and open-source software tool designed to block ads and trackers across your entire network it functions as a DNS server intercepting name server lookups and if it finds domains known for serving ads or trackers it filters out those sites returning add and tracker free content to your browser to learn more about adguard home check out the link to their GitHub page which you'll find in the description of this video let's get into the setup and we'll start by installing container manager from the package Center once installed you'll want to bring up file station and create an adguard folder under the docker shared folder then within the Edgard folder create the config and data sub folders once that is done we can start up container manager select project and create a new project here you'll want to give the project the name set the path to the adguard folder that we just created select create Docker composed jamble for source and paste in the host network yamel configuration which you'll find in the description of this video an important thing to note is that Network Mode is set to host which basically Maps ports defined by the container to the corresponding ports on your sonology Nas what this means is that your sonology Nas can't already be using specifically ports 3000 which is used to access the Edgard home dashboard or 53 which is the default DNS server Port if it is the project will fail to build and you'll want to check out the bridge network setup which I'll cover a little later in the video now let's run through the remaining steps to complete the setup and start up the Edgard home project at this point Edgard home should be running and you'll want to open up a new browser tab enter in the IP address of your sonology Nas along with Port 3000 to bring up the adguard home welcome window where you'll want to click get started to continue with the setup from this window change the admin web interface port to 3000 which is the port we're currently using next from this authentication window enter in a username and password you would like to use to access the Edgard home dashboard click next on this configure your devices window then click open dashboard from this window to bring up the admin web interface login screen you'll then want to log in with the username and password you just set up to get into the Edgard home dashboard now that the project is running you'll want to configure your DHCP server to use adguard home as its DNS server most of you will need to configure this setup on your router and in my case I have a sonology router so I'll bring up the DCP server settings and change the primary DNS server to the IP address of my sonology Nas that I'm running adguard home on next you'll need to renew the DHCP lease on your system to make use of the new DNS server setup on my MacBook I can do this by bringing up my Wi-Fi settings and click on details from here I'll click on TC P IP select renew DHCP lease and apply the changes now if I bring up details once again and select DNS I can see the DNS server I'm using is now set to the IP address of my sonology Nas that is running Edgard home at this point I'll test that adguard home is working by loading a few web pages that I know have adds on them then bring up the Edgard home dashboard and click refresh statistics where we can see that ads are being blocked there are a few things I'd like to point out about this setup one is that you'll see individual clients using adguard home listed in the top Client List which is a feature I really like about the host networking mode the downside of this setup which I touched on earlier is that you can't change the default port numbers used by the container which you can do with the bridge networking mode which I'll go over next before going through that setup up I'll revert the DHCP DNS server on my router back to default and renew the DHCP lease on my MacBook so it reflects the DNS change that was done on my router now back in DSM you'll want to stop the aduard project bring up file station delete and recreate the config and data sub folders under the aduard folder to have both once again be empty folders then back in container manager bring up the adguard project and edit the yaml configuration here you want to remove the network mode host entry to set up the project in bridge mode and configure Port mapping for my setup I'll change the host port to 3001 which will map to Port 3000 within the adguard container we'll also want to map hostport 53 to the container's port 53 to allow clients to access the DNS server Edgard home is running also if you want to cut and paste this yaml config or if you want to start off with a bridge network setup you'll find the full yaml configuration listed in the description below next you'll want to save the changes to build and start the project now you'll want to bring up the adguard home welcome window once again and in my case what I'll do is bring up the tab I had the adguard home dashboard running in change the port to 3001 which is the host Port configured to access the Edgard home container and run through the setup once again for the admin web interface you'll want to change the port to 3000 which is the port used to access the admin web interface from within the container and proceed through the remainder of the setup you'll find that when you click open dashboard you'll be directed to Port 3000 so you'll need to change the port back to 3001 to access the the adguard home dashboard login screen where you'll now be able to log in at this point you'll want to update your brower's DHCP DNS setup once again renew the DHCP lease on your client like I'm doing on my MacBook I'll then reload those web pages that contain ads that I tested earlier then bring up the Edgard home dashboard where we can see that DNS queries are taking place we don't see any block domains yet but after a few more queries block domains started showing up in my Edgard home dashboard one thing I want to point out is that with a bridge network setup all clients will share the IP address of the Edgard home Docker container and won't show up individually under the top client section add and tracker blocking will still work fine but you just don't get the client details you would with host networking the benefit of a bridge network setup is that you can Define host ports you'd like to use like we did where we assigned Port 31 as the host port to access the Edgard home admin web interface there's also a third network setup that allows Edgard home to both allow for individual clients to be displayed under top clients and allow custom hostport numbers to be used using a Mac VLAN Network which I'll cover in a separate video that I'll release shortly so consider subscribing if you'd like to be notified when that video comes out also Edgard home works similarly to Pyle and I have a few videos on py hole that you may want to check out listed here on screen lastly if you'd like to support my work or hire me for a sonology project you are working on check out the links either here on screen or in the description below thanks so much for watching

Channel: Digital Aloha

Views: 1,136

Keywords: synlogy nas, adguard, adguard home, ad blocker, pi-hole alternative, netowrk wide ad blocking, host network, bridge network, adguard home docker, synology container manager, adguard home dashboard, synology

Id: xx6Co3d_Jm8

Length: 8min 25sec (505 seconds)

Published: Mon May 20 2024