On my main Windows machine, the network connection is both configured with IPv4 and IPv6, using the AdGuard Home DNS Server for IPv4 but using my ISP's DNS Servers for IPv6. I also have IPv6 properly configured on my Tomato router and my main Windows machine. In my Tomato router dnsmasq configuration, I push the 192.168.0.253 DNS Server to all clients in both the main and guest networks. With Docker MACVLAN networks, the host (Synology NAS) cannot access the containers (DNS Server) and to get that working I have a MACVLAN interface in the host itself ( based on this guide). The DNS Server Docker container has it's own IP using the Docker MACVLAN network driver. 
The DNS Server running in a Docker container has an IP address of 192.168.0.253 (main network).
The Synology NAS has an IP address of 192.168.0.99 (main network). The guest network cannot access any client on the main network with the exception of the DNS Server and even for that, only port 53 is allowed. I have two subnets, one is the main network the other is the guest network. I have a Docker container running AdGuard Home (the DNS Server). To do this, we’ll need to SSH into our Synology NAS and issue the following, substituting the subnet to suit our needs: gateway, subnet, range being AGH’s static IP and ag_network will become the interface name in Docker) sudo docker network create -d macvlan -o parent=ovs_eth0 -subnet=192.168.1.0/24 -gateway=192.168.1.1 -ip-range=192.168.1.198/32 ag_network Setting upįire up Docker and grab adguard/adguardhome from Registry, using the latest tag.Ĭreate a Container using the image you’ve just downloaded and select both your current bridge and ag_network networks.As you may have noticed I've been posting a few questions about some problems I was having while setting up a custom DNS Server (using AdGuard Home for ads and trackers blocking) and now I reached to another problem related to IPv6.Ī bit of context of my whole setup for this: Double check your interfaces using ifconfig. 
It is highly advisable to expose your AGH instance to the network as a separate entity using Docker’s built-in MacVLAN support.įirst, if you had Virual Machine Manager installed, chances are that your physical network interface has been renamed to something like ovs_eth0. Just sold your Raspberry Pi and looking for an alternative to a containerised PiHole instance? There are a few reasons why you might consider using AdGuard Home for this very purpose.
0 kommentar(er)
