AdGuard Home: A world without ads and trackers!

You might have heard about Ublock Origin or PiHole, let me introduce to you AdGuard, and especially AdGuard Home!

AdGuard Home: A world without ads and trackers!

You might have heard about Ublock Origin or PiHole, let me introduce to you AdGuard, and especially AdGuard Home!

How does it work?

AdGuard Home is a network-wide software for blocking ads & tracking. After you set it up, it’ll cover ALL your home devices, and you don’t need any client-side software for that. With the rise of Internet-Of-Things and connected devices, it becomes more and more important to be able to control your whole network.

By running AdGuard Home on your home server, you will be able to use it as DNS and let it filter all ads and trackers on ALL your devices! The world without ads and trackers is yours!

So what are the differences with UBlock Origin and PiHole?

You can easily install it on a Raspberry Pi for example. On my side, I made the choice to run it on my Synology NAS through Docker.

Setup via Docker

First challenge: the port number!

Rares are the devices and routers where you can easily setup a custom port number for your DNS server. Therefore, you need to be able to expose the port 80 of your server hosting AdGuard Home (and a bench of other ports), which is kind of tricky on a Synology NAS.

I finally find out a solution, using a virtual network with a dedicated IP address to run the container inside it. And as it's a brand new dedicated IP address, all ports are available!
With the help of Docker macvlan, I set it up as below in my docker-compose file.

    driver: macvlan
      parent: eth0
        - subnet:

Few explanations regarding this macvlan setup:

  • driver_opts.parent represents the source to bring internet to this macvlan. As my Synology NAS is connected through its first Ethernet port, its the classical eth0. You can easily check the name of your interface by running "ifconfig" in ssh
  • ipam.config.gateway is the address of your network router
  • ipam.config.subnet is the subnet address matching your gateway
  • ipam.config.ip_range is the range of IP this macvlan is going to deliver to any devices on it. I have defined to get a range from 193 to 222 to avoid any conflict with my network router DHCP which is not delivering those addresses. You can define your range with any calcultator available online.

Nevertheless, if you are already a macvlan's expert, you might know about the restriction access between a macvlan and its host. No worries, a bypass is explained in this article!

When using macvlan, you cannot ping or communicate with the default namespace IP address. For example, if you create a container and try to ping the Docker host’s eth0, it will not work. That traffic is explicitly filtered by the kernel modules themselves to offer additional provider isolation and security. See Docker Macvlan Documentation.

Docker compose

Now it's time to build your docker compose completely and don't forget to create folders for your volumes before running!

version: "2"
    container_name: adguardhome
    image: adguard/adguardhome:latest
    hostname: adguardhome
    restart: always
    domainname:         # If you plan to expose it outside
        ipv4_address: # Fix the IP address inside your range
      - PUID=1026
      - PGID=100
      - TZ=Europe/Paris
      - 53/udp 
      - 67/udp 
      - 68/tcp 
      - 68/udp 
      - 80/tcp 
      - 443/tcp 
      - 853/tcp 
      - 3000/tcp 
      ServerIP:  # Need to match ipv4_address
      VIRTUAL_HOST:  # Match hostname + domainname
      WEBPASSWORD: ""                        # Add password (if required)
      - /volume1/docker/adguard/config:/opt/adguardhome/conf 
      - /volume1/docker/adguard/work:/opt/adguardhome/work 
    driver: macvlan
      parent: eth0
        - subnet:     # My network subnet
          gateway:       # My network gateway
          ip_range: # Range from 192 to 222
            host: # To avoid the network to give this IP. Reserved for mynet-shim

How does it look on my Synology NAS:

      |_ docker-compose.yaml
      |_ config/
      |_ work/           

And now, you just have to launch your docker-compose file with the following command cd adguard && docker-compose up -d

You can now access the AdGuard Home interface via the IP address you defined for it, in my case. I will not detail here all features of AdGuard Home in this article as its documentation is pretty complete, but I can mention that the interface is clean and super straight forward!

Setup AdGuard Home as your default DNS

As your DNS is now running and fully configured, let's send it some traffic to resolve and filter! It's time to kill some ads and trackers!

You can decide to either doing it manually on each device either directly in your router.


Even if the ultimate solution to remove all ads on ALL your device is the next method to come, doing it manually on your computer only, as a first step, will help you to see the incoming traffic and to do the right setup on AdGuard Home before deploying it on all your devices. I will not enter into details about the How-To, you can find some good guides below.

In your router

The objective is to define your AdGuard Home as preferred DNS inside your router directly, so it's going to spread it automatically to all your devices (You might need to wait a bit or to restart the devices so they can get the update!)

This setup is super standard on most of the router but can be very specific to find. Look of "Preferred DNS".

I'm using a UniFi USG router and this setting is located in Networks > LAN > DNS (DHCP Name Server).

Some routers give you the option to setup a secondary one in case of the first one is not responding, I'm using Quad9 (

Advanced configuration

Here are some of the DNS blocklists I'm currently using:

Enjoy a world without ads and trackers!

Looking for help?
If you are looking for some help or want a quick chat, please head over to the Discord Community!