DNS Leak #2451
Unanswered
mattdale77
asked this question in
Q&A
DNS Leak
#2451
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have finally managed to solve this but I'm wondering if there is a cleaner way. I've got tailscale set up with a Mullvad gluetun container as an exit node. It worked just fine as a VPN but it was leaking DNS to cloudflare which I did not have configured anywhere. It took me a long time to realise that this was being injected by gluetun and not my own servers somewhere. Once I found it that it was gluetun I seemed to be able to remove the cloudflare leak and introduce a leak to whichever DNS the host had by adding DNS_KEEP_NAMESE|RVER=on. This was at least understandable but I was still leaking.
I solved this by adding the following
dns:
This fixes the DNS into Mullvad, I'm not sure if there's a downside.
Can anyone tell me if this is the right way to solve this problem or if I can do it more cleanly? Basically I want to use the VPN DNS for everything beyond my network (although that could be everything as tailscale will deal with local resolution)
Beta Was this translation helpful? Give feedback.
All reactions