Top
Best
New

Posted by frostbyte7 1 day ago

So my ISP was hijacking my DNS(www.karthihegde.dev)
157 points | 116 commentspage 2
aand16 11 hours ago|
How is this not illegal... isn't what the ISP doing "hacking"?
figmert 9 hours ago||
Illegal, where exactly? In various western countries ISPs are by law required to block some websites. In other countries, ISPs ar eby law required to have escape hatches to be able to shut down the internet. In yet others, everything runs behind a firewall. Take your pick, I guess?
noselasd 8 hours ago|||
Very few, if any, countries makes this illegal.

Some countries have laws around Net Neutrality or Open Internet that can protect you from this, but even those countries have other legislations that can superseed that in specific cases. (e.g. hijacking DNS can be completely legal for some child protection laws, or to uphold laws that makes some web sites illegal)

throwawayffffas 9 hours ago||
The hijack is probably legally mandated. The site he was trying to reach is a torrent site.
aand16 1 hour ago||
Interfering in communication. If I understand correctly the ISP rewrote the author's communication with an external DNS/third party.
itopaloglu83 8 hours ago||
I’m using NextDNS over https and frequently experience connection freezes with both Spectrum and T-Mobile. I don’t know what they’re trying to do, but I’m not happy with the way they’re trying to block basic services.
unethical_ban 1 hour ago||
Here is my self-documentation for home DNS setup: https://docs.zeropolis.net/doku.php/tech:homedns

Unlike OP, I have all my DNS route completely to my home DNS server, and only make changes to that container and my VM host during a "change window" meaning not during work hours. I block port 53 outbound entirely and have host entries for the two domains that my DNS server uses for DoH. If I had a better firewall on the edge, I would leave 53 open for my DNS container, but this workaround seems suitable enough for the home network.

j45 2 hours ago||
It's best to treat your ISP's DNS as not being in your best interest, and actively against you getting your full internet speed and responsiveness.

Set an external DNS server on your router, or learn to run your own locally.

arcfour 11 hours ago||
> Although your regular internet traffic is encrypted with TLS, your ISP can see the hostname during the TLS handshake (SNI).

https://support.mozilla.org/en-US/kb/understand-encrypted-cl... not anymore, with many (not all) sites.

gib444 11 hours ago|
Very few of the top 10k sites support ECH

https://divested.dev/misc/ech.txt

mgoetzke 8 hours ago||
Deutsche Telekom did that too on my DSL line once, took some arguing to them suddenly 'do nothing' but it suddenly 'worked'
Sha1rholder 12 hours ago||
Sounds familiar to a Chinese
amstan 11 hours ago||
Reminds me of the Xfinity "Your personalized WiFi summary" emails. Despite returning their router, using a third party almost-layer-2 modem, my own openwrt router (with its own wifi, thank you very much), their emails seem spooky.

They have a counter of all of my devices, somehow (i mean... i guess their count is wrong, but it's infuriating that they try to keep track).

gruez 7 hours ago|
All of that could be done without "ISP was hijacking my DNS". DPI/SNI sniffing is more accurate and allows you to get more detailed statistics (eg. "20% of your bandwidth goes to youtube"
tripdout 5 hours ago||
We need root DNS servers that support DoH/DoT.
eqvinox 3 hours ago|
No. That's not within the design function of the roots.

It's very much part of the design that roots and caches are separated. The security properties necessary between root and cache (authenticity) are fulfilled by DNSsec, not DoT/DoH (primarily privacy). And most TLDs are DNSsec signed, so this part is in fact OK. (Both give some level of tamper protection, in a different manner though.)

You're probably saying this because you run a local cache directly against the roots. If you need DoT/DoH, you shouldn't be doing that and rather forward your queries to a cache somewhere else.

(To make sure there's no misunderstanding here: DoT and DoH do absolutely nothing to guarantee the data you're getting is what the roots/TLD/owner published. It only ensures you're talking to the cache you think you're talking to. The cache can serve to you whatever it wants.)

mariofdistrust 1 day ago|
my mobile network carrier blocks quad9
486sx33 19 hours ago|
[dead]
More comments...