Privacy

32120 readers

426 users here now

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

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago

MODERATORS

Is it possible for my ISP (or the router in my network) to modify results of someone else's DNS? (lemmy.ca)

submitted 4 months ago by hackysphere@lemmy.ca to c/privacy@lemmy.ml

8 comments fedilink hide all child comments

I am wondering if an ISP or network admin on my network would be able to change where a DNS server is located at (ex: if a DNS server is located at 132.192.175.210, the ISP/netadmin can redirect it to their own server at 11.29.102.201 to change where the DNS records point to). Does DNSSEC and DoH/DoT combat this, and how? Why is it safe to use a domain for DoH/DoT if it requires going through insecure DNS to get to a secure DNS?

you are viewing a single comment's thread
view the rest of the comments

[–] rasensprenger 14 points 4 months ago* (last edited 4 months ago)

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.