It won't work unless you first add a ULA to your device's interfaces, but you can use instead to substitute the router's ISP-assigned global address, or even which uses the router's link-local address, though it sounds like you'll be placing the full static IPv6 address of your AdGuard Docker instance there, considering your stated objective. The final segment,, tells dnsmasq to determine the subnet's current ULA (Unique Local Address) and announce it as the IPv6 DNS server to clients, whatever it may be. Which brought me the question, should I even be using IPv6 on my Tomato router and my Windows machine? Should I just disable IPv6 on the router and forget about this? Or should I take the time to configure my AdGuard Home container, MACVLAN networks, firewall rules and all that to work with IPv6 too? Do I have anything to gain from using IPv6? This is a problem because for this particular Windows machine, the AdGuard Home DNS Server won't be used that much. Now, what's my problem? Windows will pick either the IPv4 or IPv6 DNS Server and if I'm not mistaken will give priority to the IPv6 one, only using the IPv4 one if needed. 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).
0 kommentar(er)
