Live data from Hacker News

A cartoon intro to DNS over HTTPS

hacks.mozilla.org

81–90 of 137 posts

Re: A cartoon intro to DNS over HTTPS

#81
post #3

"Threats to users' privacy and security are growing." s/privacy/&, autonomy/' Case in point about autonomy is on HN front page at present: https://news.ycombinator.com/item?id=17196888 The author cites a hypothetical example where a user shopping at Megastore is blocked from accessing her preferred source of DNS data in order to prevent her from checking a price. Extending this hypothetical, imagine if in response to…

s/single HTTP request/single connection/

Re: A cartoon intro to DNS over HTTPS

#82
post #73

Was just wondering... what value will DNS over HTTPS provide if/when we all move to IPv6 and presumably everything could potentially be identified by IP address directly? Will datacenters/ISPs be incentivized to do NAT with IPv6 or have some other way of introducing indirection into the routing?

Think about Cloudflare itself. Millions of websites hosted behind a handful of IP addresses.

Re: A cartoon intro to DNS over HTTPS

#83
post #55

As a cynic I would say this is an attempt by Google and Cloudflare to collect DNS data. Why else would they provide this service for free? Both Google's [1] and Cloudflare's [2] DNS privacy policy prohibits them from storing personally identifiable information or from correlating DNS information with other Google data coming from the same IP/account but it does allow them to store information about which domains are…

> Why else would they provide this service for free? Cloudflare runs the largest authoritative DNS server for their customers. The best way to make the DNS server faster is to make users query it directly. For Cloudflare-hosted domains, instead of: User → ISP's DNS resolver → ns.cloudflare.com. you get: User → [ 1111 → ns.cloudflare.com. ] where the latter two are on the same machine.

I work at Cloudflare, this is correct.

1.1.1.1 runs on our existing hardware deployed around the world, it costs us very little. When you use it it improves performance for the 8 million or so sites we sit in front of, that's our actual business.

Re: A cartoon intro to DNS over HTTPS

#84
post #73

Was just wondering... what value will DNS over HTTPS provide if/when we all move to IPv6 and presumably everything could potentially be identified by IP address directly? Will datacenters/ISPs be incentivized to do NAT with IPv6 or have some other way of introducing indirection into the routing?

Think about Cloudflare itself. Millions of websites hosted behind a handful of IP addresses.

So we go back to re-centralizing for privacy? I love Cloudflare, but... if that's really the answer to this... sigh.

Re: A cartoon intro to DNS over HTTPS

#85
post #53

Earlier quoted context omitted.

DNS over HTTPS is actually a lot slower to resolve than traditional UDP DNS.

Yes, but only because of TCP and TLS connection overhead. Once the connection is established, response time is similar to UDP.

Does the connection get reused?

Re: A cartoon intro to DNS over HTTPS

#86
post #16

As a cynic I would say this is an attempt by Google and Cloudflare to collect DNS data. Why else would they provide this service for free? Both Google's [1] and Cloudflare's [2] DNS privacy policy prohibits them from storing personally identifiable information or from correlating DNS information with other Google data coming from the same IP/account but it does allow them to store information about which domains are…

Cloudflare itself never made sense to me. What possible incentive do they have to stop their primary purpose (DDoS protection) - They have value in promoting the behavior. Whats worse, is everyone and their dog is using them. What happens when they push a bad config to their core routers, or foobar their anycast?

Um .. you remember how they spammed random password data and memory all over the Interwebs right?

https://www.pcmag.com/news/351962/cloudflare-leak-exposed-da...

Re: A cartoon intro to DNS over HTTPS

#88

As a cynic I would say this is an attempt by Google and Cloudflare to collect DNS data. Why else would they provide this service for free? Both Google's [1] and Cloudflare's [2] DNS privacy policy prohibits them from storing personally identifiable information or from correlating DNS information with other Google data coming from the same IP/account but it does allow them to store information about which domains are…

As an ISP, I'm skeptical of the motivations of big CDNs and Google in general, but it's becoming an ietf standard. I run recursive resolvers for clients numbering in the hundreds of thousands, with an ACL that allows only our ARIN IP blocks to query them. It is not hard to put a dns-over-https frontend in place for my clients which pulls queries from my own trusted bind9 servers. Any ISP with a clue can do the same.

For people who know how, why not just run this stuff locally? Setup your own recursive resolver on an openwrt router? Or maybe in a hosted VM close to where you live?

I know Google and CF claim they don't track this DNS information, but why even use them when you can run your own. Keep in mind CF did have a software bug that spewed SSL traffic and passwords all over the Internet[1], and they took down a website once because their CEO didn't like it[2].

[1] https://blog.cloudflare.com/incident-report-on-memory-leak-c...

[2] https://fightthefuture.org/article/the-new-era-of-corporate-...

Re: A cartoon intro to DNS over HTTPS

#89

I kind of hate this. Taking a decentralised service, and replacing it with a service provided by a small handful of tech giants. "But this doesn’t mean you have to use Cloudflare. Users can configure Firefox to use whichever DoH-supporting recursive resolver they want. As more offerings crop up, we plan to make it easy to discover and switch to them." Only defaults matter. Your average web user wont be interested in…

It does not need to be centralized at all. Any internet service provider with a modicum of Clue can install a DNS over https frontend listening on the IPs of their recursive resolvers, and pull data from their existing bind servers. This does not contain any sort of proprietary or non free software. People are free to ignore the content delivery Network provided recursive resolvers, and set up their own.

In this blog post, Firefox should encourage people who know how, to run their own. Maybe even provide/maintain some docker images for us tech heads.

I agree that immediately promoting CF doesn't seem like the best genuine idea for those who are still a part of the Firefox/Mozilla community.

Re: A cartoon intro to DNS over HTTPS

#90
post #73

Was just wondering... what value will DNS over HTTPS provide if/when we all move to IPv6 and presumably everything could potentially be identified by IP address directly? Will datacenters/ISPs be incentivized to do NAT with IPv6 or have some other way of introducing indirection into the routing?

Note that for now, if you're sniffing packets, you can learn hostnames anyway due to TLS sending SNI in the clear. That may or may not change in the future...
Post reply on HN