So my ISP was hijacking my DNS

karthihegde.dev

231 points by frostbyte7 3 days ago


simonjgreen - 2 days ago

Noting this article skips over any discussion about why, or potentially (in the eyes of the law at least) legitimate reason an ISP might do this.

Many ISPs in many countries are forced to do this for certain enforcement action that gets put upon them by their respective states for things such as age gating, censorship, monitoring, it varies state by state.

And to be clear this is in no way an endorsement of the practice, and I am confident no ISP WANTS to do this.

I am speaking here as the owner of a UK ISP (who does not currently do this).

jwrallie - 2 days ago

My workplace is messing with DNS as well, probably to filter specific websites, and I would not mind it since for the context of my usage that is perfectly fair.

But their DNS responses have latency spikes every couple of minutes of 1-2 seconds that was driving me crazy. I simply enabled DNS over HTTPS in Firefox and everything feels so smooth now.

I have no idea how my coworkers seem to be so insensitive to it.

Terr_ - 2 days ago

I fear a future where pretty much everything is trying to hack you or doing something which is indistinguishable from the meddling of a hostile actor.

I suppose the answer is politics rather than technology: Get enough people together to make a rule against it, and at least it will become niche.

daitangio - 2 days ago

Telecom Italia locks my DNS server (I cannot change it).

I ended up using PIHole as DHCP, to drive home devices to PIHole, and control my privacy.

The trick is simple: disable DHCP on your router, and activate it on PIHole. As a bonus, PIHole on my RasperryPI2 is way faster than the little chip on my provider Router, and can be patched automatically with unattended upgrades.

lxgr - 7 hours ago

> DNSSEC doesn't encrypt your DNS traffic before sending it to a resolver. It uses cryptographic signatures to verify that the DNS data is authentic and hasn't been tampered with. But the problem here remains the same: your DNS traffic is still unencrypted in transit. Which means, your ISP can still snoop on it or mess with the responses.

The "mess with the responses" part makes no sense. The point of signatures/authentication is to prevent tampering, and DNSSEC does that successfully.

For that to work, of course you need to validate the signatures on your own infrastructure and not rely on your ISP's resolver to do that.

nunez - 2 days ago

AT&T in the US does this. Traditionally they did this so that failed lookups were routed to their search engine, which of course fed users ads.

eqvinox - 3 days ago

The point of running a local unbound is indeed to turn on DNSsec validation. After that, it's the domains' fault for not using DNSsec. But at least your own stuff won't be tampered with, because you use DNSsec on your own domains, right? Right?

:-(

Coincidentally, a bunch of free wifi stuff blocks the root key queries unbound does at startup, resulting in nothing working until you get those records in there somehow (e.g. load_cache).

usacoder - 5 hours ago

I forgot to re-register my domain, ISP didn't send any notice, someone grabbed it in less than 24 hours, and was auctioning it off for $1k. F.I.

johnhtodd - a day ago

I'll throw my $.02 in here since this is getting some traction: DNSSEC validation should be used, no exceptions, no excuses. If you're running a local resolver, turn on stub validation for DNSSEC - it prevents anyone (even a DOH/DOT upstream forwarding cache) from lying to you without your knowledge. If you run a domain name: turn on DNSSEC. It's 2026 - not 2012. DNSSEC works great, we validate it on 100% of our queries, and is one of the tools needed to stop people from meddling with the DNS. https://circleid.com/posts/common-beliefs-about-dnssec-put-t...

Also, encrypt everything. DOT/DOH/DOH3/DOQ - leave no packet available for observation. Criminals, nosy network snoopers, and governments either want to know what you're doing or they want to break the integrity of the internet for profit or political reasons, and it is work to keep them out of your business.

context: I work at Quad9, one of the larger public resolvers.

unethical_ban - 2 days 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.

AceJohnny2 - 2 days ago

Which ISP was doing this? It's worth calling out the bad actors.

aand16 - 2 days ago

How is this not illegal... isn't what the ISP doing "hacking"?

hedora - a day ago

I need to mess with my local DNS resolver for unrelated reasons. Is there a way, in 2026, to setup DNS in a federated way?

I could point to ISP DNS, or 1.1.1.1 / 8.8.8.8 / etc but those are all centralized, and are all subject to surveillance and censorship laws.

DNSSEC, etc, are something, but they rely on CAs. I mostly just want some sort of system that's outside centralized control, but that can be externally audited for trustworthiness.

j45 - 2 days 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.

maeln - 2 days ago

For various reason, I also setup an Unbound who proxy to quad9 and is only accessible through DNS over HTTPS/QUIC and is behind a reverse proxy with auth (because being an open dns resolver on the internet is still a bad idea). This is nice because I can then have a dnsproxy or similar on my various devices, who all point to it and be pretty sure nothing can hijack my DNS queries. I also come with the benefit of forcing thing like a minimum TTL to avoid dumb services who decide to put a 10 seconds TTL to all their DNS entry...

itopaloglu83 - 2 days 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.

temp0826 - 2 days ago

Recently went down a little rabbit hole to get my house in order when I noticed weird things showing up at https://dnscheck.tools/ . (I don't really understand how these checks work though)

arcfour - 2 days 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.

jfyi - 2 days ago

Hardly a new thing.

Oh and btw, it's not "DNS Hijacking" it's a "Domain Helper", see: https://feross.org/shame-on-you-comcast/

pocksuppet - 2 days ago

I wouldn't publicize that you have Podman containers connecting to 1337x.cc. You have flagged yourself as probably an advanced pirate, the kind that's worth pursuing for damages.

nukanse - a day ago

Some day we will find aliens, and I wonder if we will be well prepared against their hacking or find we are naively vulnerable

Sha1rholder - 2 days ago

Sounds familiar to a Chinese

BLKNSLVR - a day ago

I do think ISPs should take a more active role is filtering DNS for their Customers, by default, but opt-out-able, against known-bad domains, or partner with public DNS providers for said service, and include options for blocking additional specific topics (ads, adult sites, gambling, social media, the usual suspects). It could be a value-add differentiator.

It should only be done as a Customer Service, however, and disclosed in a normal sized font and, as I said above, opt-out-able.

I would also extend this to say that ISPs should do the same for known-bad ASNs, and network ranges. Following on from yesterday's discussion about (p)residential proxies, blocking access to known C&C server domains and addresses at an ISP level would be a great solution.

I am, of course, looking at this through a utopian lens where ISPs aren't in bed with big tech and data brokers and other sketchy industries where profit can be made from selling out your customers' data. A 'real' ISP, you know, like 'no true scotsman'. It's all a question of trust and responsibility.

I pretty severely 'mess' with DNS on my home network and, damn, it makes using the Internet a much nicer experience. In fact, it makes using the Internet tolerable, where otherwise it is decidedly not. It could be classified as 'insecure' to not mess with DNS on any network[0].

[0]: https://www.pcmag.com/news/fbi-recommends-installing-an-ad-b...

mgoetzke - 2 days ago

Deutsche Telekom did that too on my DSL line once, took some arguing to them suddenly 'do nothing' but it suddenly 'worked'

ck2 - 2 days ago

ISP can still see exit IP unless you VPN

Cloudflare Warp is handy, complete tunnel even if not as private as real VPN

since 80% of the web is on cloudflare it accidentally makes it faster anyway

and you don't have to use the cloudflare client, you can use Wireguard

amstan - 2 days 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).

mariofdistrust - 3 days ago

my mobile network carrier blocks quad9

peter_d_sherman - a day ago

>"That's when I realised my ISP was hijacking my DNS queries and returning a tampered IP address.

[...]

Now here's the catch. DNS resolution doesn't happen over a single connection. Your resolver might have to talk to multiple nameservers to figure out an IP address, and these queries are traditionally sent over plaintext DNS, usually UDP. Which means, you guessed it, your ISP can snoop on or even tamper with your DNS traffic."

This article raises several excellent points.

Basically, unencrypted DNS requests are not private.

Even encrypted DNS, once it gets to the DNS Server wherever that is, is no longer private to the owner of that DNS server, because it is unencrypted there... it may go nowhere from there, but then again, there could be logging and/or monitoring...

And DNS servers that you think don't belong to your upstream ISP -- can be proxied/rerouted by your upstream ISP...

If those points are understood by consumers, then an average person can clearly see why there is such a market (and that's the magic word, "market") for privacy solutions, i.e., encrypted VPN's, encrypted 3rd-party DNS, IP source address anonymization, etc., etc., here in the U.S. ...

In other words, a savvy privacy company or companies could sell to all U.S. Internet customers regardless of who their upstream ISP is, or what their upstream ISP promises in terms of privacy, if (and it's a big if!) they truly understand these issues and could explain them from the ground up, one-to-one, to all such potential customers...

Yes, there are a lot of VPN and other such companies, and prior customers already (not to mention free alternatives, such as Tor (but I still have questions about the exact quality of privacy Tor actually provides given browser fingerprinting and other related technologies), but that market is still segmented, has a relatively low bar for entry, and is still "up-for-grabs" for new small companies (i.e., no need to invest billions in a datacenter of GB300's to get your first AI model out...)...

Anyway, great article.

I never considered some of these issues (or their implications!) before reading it!

tripdout - 2 days ago

We need root DNS servers that support DoH/DoT.

1vuio0pswjnm7 - 2 days ago

"DoT and DoH rely on you trusting the DNS resolver you're sending your queries to. They encrypt the connection, so your ISP can't casually snoop on or tamper with your DNS traffic in transit."

But _their_ ISP can casually snoop or tamper with their DNS traffic in transit

Because these third party caches (generally) still retrieve DNS data over unencrypted connections to authoritative nameservers

Cloudflare is one of the internet's largest authoritative DNS providers

This no doubt reduces the number of remote queries their cache has to send, but it doesn't account for domains that are not using Clouflare nameservers

It's worth considering why authortative DNS providers (generally) do not offer encrypted DNS

If this service exists then the www user does not need to use third party caches in order to have "encrypted DNS"

jon128 - 2 days ago

As a general rule of thumb, the first AS immediately outside the edge device be that a laptop with a 5G WWAN card or the router of the LAN must not be able to see anything other than QUIC or TLSv1.3, either of with encrypted hello, or IPsec or Wireguard packets.

And if the remote end is available over the local region's mesh network so to not use any commercially operated AS, even better.

current mood: https://external-content.duckduckgo.com/iu/?u=https%3A%2F%2F...

netsharc - 2 days ago

Yum, screenshots of terminal windows, which is just text...

Edit: oh wait, it finally loaded, 3x3MB images of text with scenery in the background!

ZebusJesus - 2 days ago

comcast/xfinity has been doing this for years, its called security edge

bradknowles - 2 days ago

Another reason to use a VPN you can trust, across your entire network and at all times.

z3t4 - 2 days ago

The story ended before it even started... What are the machine with the wrong IP doing? Is it just forwarding the request, or what is happening?

Tepix - 2 days ago

Why not start by

1. contact the ISP and ask wtf they are doing

2. switch ISPs