Yes, easily. DNS over HTTPS is the most common fix for that.
Privacy
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
-
[Matrix/Element]Dead
much thanks to @gary_host_laptop for the logo design :)
Unless you are verifying DNSSEC, they could intercept any outgoing DNS queries and replace the response with whatever they want, if you are using DNSSEC they won’t be able to modify the responses since they can’t create the signatures, but they could still send queries to their own server instead of your chosen server. With either of these options they can still see what you query. DNS over TLS or HTTPS is a way to prevent all of these things, since with those you know the endpoint of your HTTPS connection is the actual server with the signed certificate and the connection is encrypted.
Edit to add: it shouldn’t matter what DNS you use to look up the IP of the DoH/DoT server, because only the real servers should have the correct private key.
Yes they can, but it doesn't really matter. They can't send you a faked dns response if you are connecting to the website via HTTPS, because a fake website won't have the correct certificate.
They may block your DNS queries so you can't connect to things, but they're your ISP, they can block all of your traffic anyway.
The worst they can do by injecting their own DNS server is to track your queries, but if you're not doing complicated stuff you are telling your ISP which sites you visit anyway (because of TLS Server Name Indication) and where your traffic goes (because the ISP needs a target IP to route your traffic).
A VPN "solves" all of these problems in so far as that now your ISP has a harder time tracking you, but you just moved the problem and now have to trust whoever is running the VPN server.
100% possible, it’s how adguard and piholes work
The other thing to consider of course is that if you use DoH/DoT, you still have to trust THAT DNS authority. All you’ve guaranteed is that a secure lookup and response transaction has hit their server, not that their server is providing an authoritative result and the operator isn’t storing/selling your requests.
I believe your ISP can modify the default DNS of your router so when you connect through DHCP a device it will set that DNS, but if you manually set the DNS in your device ISP can't notice it.
They can modify the DNS packets still. They aren't encrypted or signed so the authenticity of a response packet cannot be verified. Parental controls from ISP relay on being able to snoop and modify your DNS (and SNI from TLS ClientHello packets).