A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn’t great, if contents of the website are behind a paywall maybe copy them into the post
- Don’t promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
Chat rooms
much thanks to @gary_host_laptop for the logo design :)
- 0 users online
- 57 users / day
- 383 users / week
- 1.5K users / month
- 5.7K users / 6 months
- 1 subscriber
- 2.97K Posts
- 74.6K Comments
- Modlog
I can’t speak to Android but all of those require running some DNS recursive resolver locally then pointing the OS resolver to it. While I do that already, it doesn’t really address the issue I’m getting at: the OS doesn’t natively support it.
On macOS/iOS I use a
.mobileconfig
file to point to my Dockerized DNS over TLS resolver in the cloud and it works great, but why do I need to do that rather than use the “normal” DNS preferences? Command line tools still revert to the DHCP DNS server so on macOS I run unbound to take care of that.For Linux, I’m mainly running a Raspberry Pi on Alpine Linux with unbound as well; it works great for DHCP clients that get pointed to it but (especially if this were some company LAN) all the DNS queries are still going over the LAN unencrypted.
deleted by creator