Gluetun container "needs" to leak DNS?
from Polite_Crocodile@lemmy.dbzer0.com to selfhosted@lemmy.world on 03 Oct 2024 02:08
https://lemmy.dbzer0.com/post/28913009
from Polite_Crocodile@lemmy.dbzer0.com to selfhosted@lemmy.world on 03 Oct 2024 02:08
https://lemmy.dbzer0.com/post/28913009
So, I’m trying to set up gluetun. I linked a Firefox container to it and apparently every check of DNS leaks shows that it’s leaking. Cloudflare and quad9 are the servers, the same names that I’ve set to dot providers. So I am gathering from all of this that these leaks are to be expected? And non of the DNS servers show my real IP, always one of mullvad IPS. Am I getting this right?
#selfhosted
threaded - newest
Are you sure the Firefox settings aren’t overriding your DNS?
Yes I checked
Check again, it is sneaky AF.
It was! Every DNS setting off and still I had to restart the whole stack twice
Yeah I was thinking DNS over https was sneaking in, it’s a tricky little bastard and you have to kill Firefox to change that properly.
How I imagine you responding to your singular downvoter:
<img alt="" src="https://lemmy.world/pictrs/image/727731b3-19c3-4cf3-967f-ba62eedf1ae8.gif">
Eh. If people aren’t aware of it, now they are.
Firefox has its own DNS settings. Doesn’t pay attention to the host settings.
Firefox CODE has DNS overrides. How would being in a container change this?
Not normal. Check Firefox plugins. Maybe disable that safe browsing check option I doubt that’s it but it can’t hurt.