On 2/15/2026 at 4:20 AM, Zervun said:

Hopefully this helps people out - I was poking my eyes out trying to figure this out

IF you are using the Firefox container to test, by default it has built in DNS over HTTPS which overrides local DNS settings. Go into Firefox privacy & security, scroll down to DNS and turn it OFF

Restart Firefox container and test with www.dnsleaktest.com or mullvad.net/en/check

For other containers if they have nslookup, you can use that as well

Thanks so much, Zervun, for posting this. Like you I was going in circles trying to figure out why I was getting DNS leaks while testing my VPN setup in Firefox docker container. Thanks to you, all is good. I really appreciate you taking the time to share this with the community. A.I. had me chasing imaginary rabbits. 🫤

Edited August 31Aug 31 by Burndaddy

If you, like me doesn't have the unraid server on same subnet as PC you want to reach docker from (like firefox mgmt on 8080 to actually be able to use it), you can add LAN-subnets (RFC 1918) into /etc/wireguard/wgX.conf (where X is the number of the wg-interface you want to change).

PostUp=ip -4 route add 10.10.10.0/8 via XXXXXXX dev br0 table 20Y

PostUp=ip -4 route add 172.16.0.0/12 via XXXXXXX dev br0 table 20Y

PostUp=ip -4 route add 192.168.0.0/16 via XXXXXXX dev br0 table 20Y

PostDown=ip -4 route add 10.10.10.0/8 via XXXXXXX dev br0 table 20Y

PostDown=ip -4 route add 172.16.0.0/12 via XXXXXXX dev br0 table 20Y

PostDown=ip -4 route add 192.168.0.0/16 via XXXXXXX dev br0 table 20Y

where X is gateway for unraid server and Y is the wg-number.

Example for wg8 where unraid server has gateway 192.168.1.1
PostUp=ip -4 route add 10.10.10.0/8 via 192.168.1.1 dev br0 table 208

I hope unraid doesn't overwrite these files. I've tried inactivate and activate the wg-tunnel and it didn't get over written at least.