So my ISP was hijacking my DNS
0 comments · networking
- Comments20
0 comments · networking
Story details from Lobsters ↗ · linked article on karthihegde.dev.
So my ISP was hijacking my DNS was first seen on Lobsters · Hottest on Nov 4, 2026. Since then it has appeared in 111 checks on 4 different days. Its best position was #1 of 25, reached on Nov 4, 13:51 UTC. It dropped off the list after Nov 7, 15:51 UTC. The same link also trended on Hacker News, which raises its cross-platform score.
Position on Lobsters · Hottest at every check (lower is better).
Best rank per day (UTC).
Platform metric as reported by Lobsters.
| List | Best | Days | Checks | Last seen |
|---|---|---|---|---|
| Lobsters · Hottest | #1 | 4 | 111 | |
| YHacker News · Front page So my ISP was hijacking my DNS | same link | |||
A few top-level comments from Lobsters, shortened. Read the full thread on Lobsters.
This is a great summary of common misconceptions, nicely done! If you want to test your own connection for this sort of interference, you can run OONI: https://ooni.org/install/. The project is building more capabilities, like improved middlebox detection, which should make it easier to identify who exactly is…
I hate that DNS, as a technology, is so frigged up. Off the top of my head: * As this article states, UDP DNS interception/rewriting is trivial. You don't even necessarily have to be a MitM if you have any visibility into the network, because UDP. * DNS is supposed to be scalable and redundant, but in practice, well,…
I feel like I cleared that up in the first paragraph. But if not, YES, they tamper with that traffic too. They monitor and tamper with all DNS traffic over port 53.
Archived daily, weekly and monthly lists that include this entry.
Not at the moment. It was last on the list on Nov 7, 15:51 UTC, after 4 days of trending.
#1 on Lobsters · Hottest, on Nov 4, 13:51 UTC. Trendoday checks this list every 30 minutes.
It was first seen on Nov 4, 2026 and has been on the list on 4 days (111 checks) since.