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?
Ain’t that is called DNS boot strapping and it is a common practice?
They sell it as for your own safety but they are just data mining and likely selling it as it is pretty useful info for marketers.
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.
I believe your ISP can modify the default DNS of you 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).
Yes, easily. DNS over HTTPS is the most common fix for that.
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.
100% possible, it’s how adguard and piholes work
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.
