Privacy DNS Chooser Script v1.0 "Snow Breeze"
Privacy DNS Chooser Script v1.0 "Snow Breeze"
Disclaimer : I'm the author of this project.
🚀 Privacy DNS Chooser Script v1.0 "Snow Breeze" Release!
Project source code : https://github.com/rollsicecream/privacy-dns-chooser
Dear Community,
I'm thrilled to announce the official release of the Privacy DNS Chooser Script v1.0, code-named "Snow Breeze"! This marks a significant milestone in my journey to simplify the process of enabling DNS-over-TLS with privacy-focused DNS providers on Linux systems using systemd-resolved.
Key Highlights:
- User-Friendly Setup: Easily configure DNS-over-TLS with a seamless and intuitive CLI Interface
- Privacy-Focused Providers: Choose from trusted DNS providers like Quad9, Mullvad DNS, and NextDNS (more coming soon!)
- Enhanced Security: DNS-over-TLS is enabled by default for a more secure online experience.
How to Get Started:
- Ensure you have systemd-resolved installed on your Linux system.
- Download the script from GitHub.
- Run the script with sudo to set up your preferred DNS provider.
Your Feedback Matters:
We value your feedback! Share your experience, report issues, or suggest improvements on GitHub Issues. Your insights help us refine and enhance the Privacy DNS Chooser Script.
Spread the Word:
Help us reach more users by sharing the news! Talk about it, share on your favorite forums, and let your community know about the release.
Thank you!
Man, did you really have to make it dependent on systemd?
It's designed for systemd-resolved, so I would assume that he had to. ;)
Ah, missed that. Thanks
Sorry I'm new to the networky world of things, could someone explain what TLS and DNS (seen it in settings here and there) are, and the differences between them.
DNS = Domain Name System. This is used to lookup an IP address (e.g. 123.234.54.32) from a domain name (e.g. lemmy.ml). A DNS query is one of the first things your computer does when you visit a site.
Plain DNS is unencrypted, which means that anyone with the ability to read your requests (e.g. your ISP) can see the names of sites that you're visiting.
TLS = Transport Layer Security. This is a protocol that's used to create an encrypted connection between your device and another one, in this case the DNS server. When this is used, the content of your DNS requests is hidden. Your ISP can still see that you're talking to the DNS server, but not what you're saying to it.
TLS also allows your device to cryptographically verify the identity of the DNS server. Without it, someone with the ability to modify your connection could change the responses from the DNS server. That would allow them to send you back the IP address of a server they control, rather than the real servers IP.
Ensure you have systemd-resolved installed on your Linux system.
Oh boy.
Cool project! Do you know Captive portals? Because there you need to use DHCP DNS a lot, and turn off dnssec and dot afaik
Hello! That's something that I should keep an eye on! When speaking about Captive Portals, I just assume everyone uses 4G/5G (which doesn't require these portals to be used) instead of open networks. My script already has DNSSEC disabled since it has caused some problems during testing. BTW, just a question : Are these portals very common? I haven't seen one since years now.
In Germany every public wifi, train (ICE windows block cell internetand they are currently lasering small waves in them), hotels, cafes, private wifis even if you are a guest.
Because of "data protection" everyone needs to accept TOS so every network has them.
No idea where you live but cell data is often expensive.
I just use the MullvadVPN app, my systemd-resolved is plain and insecure and Mullvad does all the secure DNS stuff. Obviously sucks and is not scalable at all.
Systemd implementing a switch that could then be integrated into GUIs, like KDE6's captive portal opener, is crucial. So for the portals you would make the DNS insecure, log in and secure it again. Best automatically.
That was also my question. A broader question is how to access services on the local network that are announced through local DNS? Like your router's web interface or any similar device.
Can you have split routing? Most queries go to our preferred DNSoverTLS endpoint, but some go to DNS53 on the local network.
This would also solve the captive portal if the host used to detect captive portals is always resolved locally.
Yes I think you can exclude local IPs in systemd-resolved