17 ms·
While I don't particularly trust Google all that much anymore, the fact that ISPs even have an opinion on this is a smoking gun that they're doing sketchy thing
by kelnos 7y ago
While I don't particularly trust Google all that much anymore, the fact that ISPs even have an opinion on this is a smoking gun that they're doing sketchy things with DNS data. There is no actual technical reason why they should care if you use their DNS servers or something else, even a private, encrypted DNS service.
- olliej 7y agoWe already know they do - they’ve injected ads + “suggestions” instead of dns failures in the past. They’ve also injected permanently unique cookies in http requests. ISPs can’t be trusted as dumb pipes, they’re closer to “clueless criminal” pipes. But I agree with you, I don’t particularly trust google either.
- tptacek 7y agoGoogle's design doesn't ask you to trust Google more than you already do if you use Chrome. It doesn't default you to Google's DNS servers, will honor your current nameservers, and will upgrade you to DoH at any of those servers who support it. I'm honestly not sure what more you could ask for from Google on this particular issue.
- judge2020 7y agoThe UI bug tracker is private so we don't know if there might also be a "select DNS resolver" option and/or a checkbox for "encrypt DNS" in Settings.
- colordrops 7y ago> Google's design doesn't ask you to trust Google more than you already do if you use Chrome. So in other words trust them with everything.
- LaGrange 7y ago> Google's design doesn't ask you to trust Google more than you already do if you use Chrome. ...well, I don't, so there. Also, this is true if I'd _only_ use Chrome, and never used other software for networking. Damn, I actually used to respect you. This is so disappointing.
- damq 7y agoA whole bunch of irrelevant retorts + a personal attack. I've never seen a comment more deserving of getting flagged than this one.
- olliej 7y agoI also don’t use chrome :p Google has promoted its own DNS service over others in the past, including for non-chrome users, and presumably would do the same when DoH (in whatever form) is the norm. I was simply saying we already know that ISPs misbehave, but presuming that Google wouldn’t is not necessarily a clear cut decision.
- rgbrenner 7y agoYes, Google used the right approach here. They honor your DNS settings, and upgrade it if it's available. Firefox, on the other hand, plans to force all of their users to trust Cloudflare by default.. and most users won't even know they made that change.
- gruez 7y ago[deleted]
- nuclear_eclipse 7y agoThe article itself says this.
- bsimpson 7y agoThe article?
- GeekyBear 7y ago>Firefox, on the other hand, plans to force all of their users to trust Cloudflare by default.. and most users won't even know they made that change. Mozilla has explicitly stated on their blog that they don't intend to make any change to a user's DNS settings without getting the user's consent. >When DoH is enabled, users will be notified and given the opportunity to opt out https://blog.mozilla.org/futurereleases/2019/09/06/whats-next-in-making-dns-over-https-the-default/ https://blog.mozilla.org/futurereleases/2019/09/06/whats-nex...
- judge2020 7y agoThis is something I really think should be opt-in, even if it's via a notification toast.
- topranks 7y agoThe problem is it’s just a banner with “ok” at the top, which clearly says “we’ve increased your privacy by (insert technical jumbo jumbo here).” As Bert Hubert pointed out, to most users it ends up looking like this: https://twitter.com/powerdns_bert/status/1123666707279695874?s=21 https://twitter.com/powerdns_bert/status/1123666707279695874...
- daedalus_j 7y agoSo it's more like HSTS for DNS? Auto-switch to encryption if our chosen target supports encryption? Because that seems MUCH more sensible than a lot of the stories/comments about this recently make it seem.
- tptacek 7y agoNo. The HSTS security model is per-site; the DoH model covers all sites. If you get DoH working anywhere, it's working for you everywhere.
- topranks 7y agoYes, as Google plan you implement it, which is fine. Most of the hulaboo is about Mozilla who are moving customers DNS queries to Cloudflare en mass, regardless of what DNS server they have already configured.
- nickodell 7y agoThat's true, but Google has made no commitment to keep it that way.
- undersuit 7y agoI still have something like 15 Spectrum Bogus NXDomains blacklisted on OpenWRT. When I set it up the page they were redirecting too was still the Charter page with a half done Find/Replace of Charter/Spectrum.
- zamadatix 7y agoActually everyone should prefer the other guy do it rather than host it themselves. Either way the bits have to be transported to the same colocated facilities it's a matter of who has to pay for and operate the servers. At least Cloudflare has KPMG audit them on their privacy claims. Better than nothing.
- maratd 7y ago> Actually everyone should prefer the other guy do it rather than host it themselves. This isn't true. If you're hosting it, you can control it and you can make sure that it's always operational. The last thing you want is a 100 phone call of "my internet isn't working" and then trying to explain it's not your fault, but rather it's "some other guy".
- zamadatix 7y agoIf Google/Cloudflare are having significant issues resolving DNS everybody is getting a call anyways.
- maratd 7y agoNot sure I understand. If you're using your ISP's DNS service, majority of your requests are going to hit their cache. You shouldn't notice any downtime as long as the cache doesn't expire.
- zamadatix 7y agoI mean if all of Google/Cloudflares anycast resolvers go tits up I'm going to get endless calls regardless if the end user can resolve a cached name or not.
- pdkl95 7y ago> If you're using your ISP's DNS service Or you can directly ask a domain's authoritative nameserver directly. Using an intermediate caching resolver isn't required. Recursively resolving the DNS query locally only requires asking a centralized nameserver for a domain's authoritative nameservers (the NS records) which can usually be cashed locally for a long time. Every other request is compartmentalized to different servers by domain delegation. Or do both; configure your local resolver to try recursively resolving a request, and fall back to the ISP (other) cache if needed.
- z9e 7y agoThey definitely are. I know for a fact that they are running massive Hadoop clusters storing information on DNS records involved in their customer traffic. If I recall correctly they mirror a lot of the traffic to analytics environments.
- everdrive 7y agoHow do you know this fact?
- z9e 7y agoI’m friends with solutions engineers at Hortonworks and Cloudera. It’s possible I’m wrong, and since this is anecdotal evidence I see “fact” isn’t a valid use here.
- windexh8er 7y agoI worked for a Comcast subsidiary in 2010-2011 timeframe. The company owned the network end to end. They had about 250k subscribers at the time across 4 states and at the time was the first DOCIS 3.0 network in the US. They were collecting DNS log data back then. I've been told that hasn't stopped and has progressed. Don't trust your ISP to not be passively monitoring. This particular ISP had closets full of old Sandvines [0] hardware as well that I ran across one day. I asked what the hardware had been used for and the answer was simply: "network monitoring for law enforcement". At the time all of that old gear had been decomm'd. But as I've said in older posts the DC had a hands off, tamper taped mobile rack that was plugged into core routing installed by a 3 letter agency while I was employed. This was pre-Snowden and post 9/11, likely courtesy of all those fun programs we found out about that Clapper denied. [0] https://en.m.wikipedia.org/wiki/Sandvine https://en.m.wikipedia.org/wiki/Sandvine
- cabaalis 7y agoWe'll know how much this will affect those TLAs when the government suddenly gets involved for some altruistic reason to block DNS over HTTPS. "Don't let google take over the internet!" "Time to break up big tech!"
- nemonemo 7y agoCould the collected DNS info be used for their own proprietary investment? I was reading a book about Koch industries and it made me think about the potential that most of the infrastructure companies could have outsized profit out of the derivative investment based on the information gathered from the business they are better known at.
- dcow 7y agoWe agree that ISPs should not need to view your browsing data without your consent. But there are many technical reasons for an ISP to want to run DNS outside the resolver privacy conversation: For one some ISPs run content filtering services. Some users prefer to concede extreme privacy for what they view as a safer browsing experience. It might not be your jam, but it exists. DNS is designed to be provider independent. It literally does not matter if a Google or Cloudflare or OpenDNS or DNSFilter or your ISP resolves requests. It was designed this way so that the system could be distributed and so that there is not a single point of failure for the internet’s arguably most important system. Its distributed nature means there are technical performance advantages to doing the above: reduced request latency, localized traffic routing and reduced bandwidth, etc. You don’t need a giant any cast network to serve DNS. You just need to use the servers closest to you.
- tptacek 7y agoThis is a pretty silly debate. All you have to do is look at AT&T's DNS, see it hijack NXDOMAIN to send you to ad sites, and know that mainstream ISP DNS isn't trustworthy. We don't need to weigh up counterfactuals.
- dcow 7y agoI’m not saying that some ISPs aren’t malicious. But to say there is no reason for an ISP to serve DNS is absurd.
- tptacek 7y agoThere is no reason for ISP customers to use ISP DNS, given the available alternatives, and this will become even clearer as more people boot up DoH resolvers as alternatives to Cloud Flare.
- dcow 7y agoAgain this is absolutely false. Your ISP, and nobody else, can deliver the lowest latency and quickest path DNS resolution short of other providers paying ISPs for last mile fog boxes (as some DNS providers do). Why can’t my ISP support DoT? But that also highlights a huge misconception about DoT/DoH: it only provides privacy to the resolver. It does not make your requests private in the eyes of the server or spanning the recursive queries that may be required during resolution. I’m not particularly compelled to trust Cloudflare more than OpenDNS or whatever. It’s the same situation with VPN. Anyway it’s well known that the actual solution for people concerned with utmost privacy is a round robin resolver selection strategy. It’s super easy to implement... why aren’t browsers providing this type of option?
- beached_whale 7y agoCould be caching too. Bunch of services like youtube and netflix, at least used, use DNS to direct users to local servers. This enabled a better experience for the users and lowered the amount of bandwidth
- aussieguy1234 7y agoThey also used this method to block region restricted content. Here in Aus Foxtel has a monopoly on all the good shows, they charge >$100 per month if you want access to everything on their crappy, ageing cable tv network. After Netflix blocked the vpn workaround, alot of people went back to torrenting
- beached_whale 7y agoI wonder if that will be a side effect of this. If the default is DNS via Google, then sites can differentiate on that and do nasty things like block non-google or give different results.
- clatan 7y agoThey do use that information, it's not necessarilly sketchy. They run analytics just like everyone else. In fact, one could argue Google's huge push for https was primarily motivated to deprive service providers of valuable data that Google has anyway.
- ryukafalz 7y ago>They do use that information, it's not necessarilly sketchy. They run analytics just like everyone else. First of all, I think the extent of the data collection that many companies engage in is sketchy. That aside, if a website runs analytics that you don't like, you can stop using it. There are usually alternatives, if you're willing to give up some convenience. But if your local ISPs are monitoring you, not using the internet isn't really an option these days. I really wish we didn't have to treat our ISPs as adversaries in that regard, but we've been at that point for a while.
- tannhaeuser 7y agoExactly; it's just the same old story with Google. We all know ISPs and Telcos are greedy af, but when Google is getting into providing DNS, they do it to close a loophole (from their point of view) where web visit sensor data is going to someone else; they really think they own the Internet. In this particular case, even if Google succeeds in establishing DoH via Chrome (and, sadly, also Firefox), ISPs will still get to see your IP data; they could try reverse-DNS lookup to get back domains, but this is much less targetted ever since HTTP/1.1 shared hosting. At the same time, Google is also engaged in AMP such that requests for many sites go to a single IP, with the actual requested site SSL-encrypted. What will happen next is that Google will, via piecemeal extension of HTTP/3, fuckup TCP/IP even more. I hope somebody in regulation will finally stop Google and others to monopolize the web.
- kelnos 7y agoI consider most analytics use cases to be sketchy. To me, the onus should be on the company to prove to me that their use is not sketchy.
- belltaco 7y agoIt used to be illegal for ISPs to use web browsing data for advertising purposes but the Republican House, Senate and President passed a law allowing them to make it an opt-out. https://arstechnica.com/tech-policy/2017/03/for-sale-your-private-browsing-history/ https://arstechnica.com/tech-policy/2017/03/for-sale-your-pr...
- deleted 7y ago[deleted]
- calmworm 7y agoGood article, but no link or details on how to actually opt-out?
- GoblinSlayer 7y agoUp to implementation: https://arstechnica.com/information-technology/2017/03/how-isps-can-sell-your-web-history-and-how-to-stop-them/2/ https://arstechnica.com/information-technology/2017/03/how-i... all the major ISP lobby groups signed on to a voluntary set of privacy principles based partly on the FTC framework. They specifically pledged to follow FTC guidance for opt-in consent before sharing sensitive information and to “offer an opt-out choice to use non-sensitive customer information for personalized third-party marketing.” Browsing history would be subject to an opt-out system. Harris encourages Internet users to go to their ISP’s website or call the ISP to figure out exactly how they can opt out of tracking. It’s not convenient, but the option should be there.
- DaniloDias 7y agoI have this adversarial opinion that I think is very unusual. Would love to hear your perspective. Google pissed in the punch bowl by offering google fiber. This forced the carriers to perceive google as an existential threat they are absolutely dependent upon for cheap ass android and ISP revenue from YouTube. The only move they could make was to make google bleed. So they start offering content monetization and competing advertising platforms. Their goal isn’t to win, it’s to HURT GOOGLE. Advertising prices go down when there is meaningful competition. So shitty content monetizatuon from Comcast and VZ & ATT forces the price of google advertising down. There is a big part of me that is pulling for the carriers on this front. I’m bummed more people don’t see it this way.
- kelnos 7y agoIf the carriers were good actors that in general act in good faith most of the time, maybe (assuming your hunch is correct) I'd feel bad for them. But they don't, so I don't.
- ChuckMcM 7y agoIt isn't even all that sketchy, its just providing broad snapshots of what sites are getting traffic and which ones aren't, which is used by advertisers when they bid on their ad placements. So yeah, its going to chop off some of their revenue and they don't like it.
- sroussey 7y agoYeah, they are going to tell an advertiser that Sally Doe at IP x.y.z.a is going to the planned parenthood website. Not sketchy at all.
- rcarmo 7y agoI worked at a couple of major telcos at my country, and at the last one - where we had literally millions of active ISP and mobile users - we were approached by a company willing to pay for DNS resolver data. It is definitely a thing (and possible income source) even if you don’t do that kind of analytics yourself. But I’m fascinated by the legal implications. Right now in Portugal sites are DNS-blocked for copyright reasons (IIRC without the need for what you’d call full legal oversight, just a sort of loose arbitration with the local equivalent of the RIAA), and this is going to play merry havoc with that. (Uber’s website was also DNS blocked for a while due to hassles with licensed cabs, which was interesting because the mobile app never stopped working — can’t remember if it was an actual court order, but this should give you an idea of how technically clueless some people are over here...)
- vbezhenar 7y agoI'm living in Kazakhstan which blocks some websites. Also Russia blocks a lot of websites. I can't wait to see how eSNI will play out with all those blocks, if Cloudflare and other big networks will dare to roll it out.
- GoblinSlayer 7y agoCloudflare collaborates with censors and reserves a fixed IP for the blocked site so censors can block that IP, they don't block by DNS, eSNI won't help, use Tor.
- zzzcpan 7y ago> There is no actual technical reason There exist pure technical reasons too, from address translation to DNS-level routing and load balancing. For example for ipv6-only network to access ipv4 resources there needs to be something like NAT64 embedding ipv4 addresses into ipv6 ones, but that would require overwriting DNS responses with DNS64 to actually work [1] [1] https://en.wikipedia.org/wiki/IPv6_transition_mechanism#DNS64 https://en.wikipedia.org/wiki/IPv6_transition_mechanism#DNS6... Keep in mind, encryption is not privacy. Encrypting DNS queries to a 3rd party resolver doesn't improve your privacy, it's a fight for control, not privacy. ISPs will still violate your privacy to the same extent, except said 3rd party will be able to do that too. If your ISP is not trustworthy the only way to save yourself from it is to use something like a VPN which effectively gives you a different ISP of your choice.
- knorker 7y ago> DNS-level routing and load balancing How do you mean? Why should my ISPs hijack communication between me and a content provider and reroute it? This is as if I'm in a phone meeting and when I say "let me call you back at 15:00" the phone company injects "19:00" instead, because that's a time the phone network is less loaded so it'd help them. > NAT64 embedding ipv4 addresses into ipv6 ones NAT64 is a good point, actually. But at least in 2019 if you're on IPv6 and switch to your own DNS server that doesn't do DNS64, then it just plain won't work. I doubt Firefox or Chrome will have implementations that break like that. > If your ISP is not trustworthy Or country.
- zzzcpan 7y agoSome authoritative DNS servers may respond with incorrect IP addresses for specific IP subnets of an ISP (i.e. pointing to unreachable or slow far away servers), so it could be useful to fix this either statically or by forwarding domains to another DNS resolver which gets proper responses. Things like that.
- knorker 7y agoMy experience is that things like that will obviously break more than it fixes. One cannot assume to know better between two third parties like that. Half of global loadbalancing is getting around ISPs doing stupid shit they shouldn't have been messing with.
- mcnichol 7y agoThere has been an agenda against DoH from the start. China is attacking it, ISP's are attacking it, all with loose arguments and fear-mongering.
- jcranberry 7y agoExcerpt from the letter sent to Congress. >Moreover, the centralized control of encrypted DNS threatens to harm consumers by interfering with a wide range of services provided by ISPs (both enterprise and public-facing) and others. Over the last several decades, DNS has been used to build other critical internet features and functionality including: (a) the provision of parental controls and IoT management for end users; (b) connecting end users to the nearest content delivery networks, thus ensuring the delivery of content in the fastest, cheapest, and most reliable manner; and (c) assisting rights holders’ and law enforcement’s efforts in enforcing judicial orders in combatting online piracy, as well as law enforcement’s efforts in enforcing judicial orders in combatting the exploitation of minors. Google’s centralization of DNS would bypass these critical features, undermining important consumer services and protections, and likely resulting in confusion because consumers will not understand why these features are no longer working. This centralization also raises serious cybersecurity risks and creates a single point of failure for global Internet services that is fundamentally at odds with the decentralized architecture of the internet. By limiting the ability to spot network threat indicators, it would also undermine federal government and private sector efforts to use DNS information to mitigate cybersecurity risks.
- necovek 7y agoWhile I definitely agree with the sentiment, I would much rather browsers used my own caching DNS server that I can configure to talk to root nameservers: this would be the best of both worlds (ISPs can't track me, and I wouldn't be handing data to another party either, except, well, root servers). I am sure it's going to be possible, but compared to setting it on my DHCP server, now every client's browser would need reconfiguration.
- cm2187 7y agoI don’t understand how that achieves anything. If your DNS server is in the cloud, your ISP can still see your unencrypted queries to that server. If it is at home, your ISP can still see the unencrypted queries of that server to the root servers. Unless you encrypt the traffic, DNS is transparent to the ISP whichever way you set it up. And unless you are also using a VPN, the ISP can learn most of what it can learn with DNS just by looking at the IPs you send packets too. Most commercial websites that matter aren’t sharing IPs.
- necovek 7y agoOh sure, you are right. But the thing with collecting heaps of data is that it needs to be harder. If my ISP is going to filter and process all packets in realtime, sure they can get a lot of unencrypted stuff from me. In essence, other than heavy censoring countries like China, I don't think most ISPs do that (a number of users doing that is pretty small, so the effort on their part is not worth it). And as you and others have said, it can be done by looking at IP addresses i connect to as well. What I do achieve is that nobody has a "full" picture of me, but only some subset of data that I transmit. I also use two independent ISPs in a loadbalancing/failover configuration, so that helps with the cause as well, thougb my primary use is fail-over since I am in this internet business :)
- goguy 7y agoHere in the UK sky recently pushed out an update to their firmware which made it impossible to use another DNS server other than theirs. There was a decent amount of push back, I managed to get them to downgrade my firmware but who knows how long that will last before they "accidently" update it again.
- knorker 7y agoBT's DSL router/modems also only hand out BT DNS servers. You have to turn off their DHCP server and run your own to be able to hand out anything else. Their tech support (the one that's "if we solve the problem we'll charge you") said they could not solve this for me.
- chopin 7y agoDon't you run an own router/firewall behind the ISPs? I own my internet facing router AND I run a second one for sensitive parts of my network. As well, I run an own recursive resolver.
- mavhc 7y agoWhat's the best way to tell if they're intercepting queries to other dns servers and replying themselves? Say I manually set my dns to 1.1.1.1, is there a way to tell if the replies are really from 1.1.1.1?
- belorn 7y agoWith no changes to your setup it is actually impossible. DNS as it currently exist is a plain text protocol. If you run your own dns server at your local machine you can enable DNSSEC, which will protect against manipulations for domains that has that enabled. A recursive dns server is pretty easy to setup and it a step towards running your own authoritative server in the future for private domains. If you want to resolve using googles DNS servers and be sure it is really them then the only method that I know that is also supported by google would be DoH. The other encryption method they support, DoT, do not provide authentication and draft-bortzmeyer-dprive-resolver-to-auth-00 is to my knowledge not implemented by google. If you want a bit more privacy and have a mix of the two above then go with a VPN or build one yourself. Just note that without DoH you won't be authenticating between the VPN and google, so I would just use a resolver at the VPN.
- techslave 7y agoif the mechanism is DoH then in this age of non neutrality they do care. it makes it one nanobit harder to throttle (er, optimize) traffic because they capture DNS along with bulk web traffic. let’s not munge it up either. they don’t care about encryption per se. they care about 3rd party resolvers.
- neop1x 7y agoIt's not ISP's business to spy on and modify any requests. Their business is to provide connectivity. Period. People can use antivirus and specialized blocking on different level if they need to block something.