22
Gluetun container "needs" to leak DNS?
(lemmy.dbzer0.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 03 Oct 2024
22 points (100.0% liked)
Selfhosted
40153 readers
205 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
Are you sure the Firefox settings aren't overriding your DNS?
How I imagine you responding to your singular downvoter:
Eh. If people aren't aware of it, now they are.
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.
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?