9 ms·
DNS over HTTPS–What Is It and Why Do People Care? [pdf]
- GuyPostington 7y agoThis links directly to a PDF. Reader beware.
- numlock86 7y agoWhat do you mean? This is pretty common here. Nevertheless it should be included in the title if that is what you are getting at.
- romaniitedomum 7y agoYes, putting PDF into the title is considered polite.
- pushrax 7y agoOn the other hand, if you don't want to open pdfs by accident, use "Always Ask" .. https://support.mozilla.org/en-US/kb/disable-built-pdf-viewer-and-use-another-viewer https://support.mozilla.org/en-US/kb/disable-built-pdf-viewe...
- Gaelan 7y agoWhat's wrong with links to PDFs? A concern with malware?
- dhritzkiv 7y agoI'm not sure about these days, but I do remember being hesitant about opening PDFs 12+ years ago, before I switched to MacOS (Safari has always had very good PDF display ability via OS X), and before all the major browsers had built-in PDF display (PDFs would often be downloaded as a file, which would trigger the opening of some PDF viewer shareware pre-installed on Windows). Terrible UX back then.
- notzuck 7y agoYeah that was true back then. Opening a PDF link on windows 2000 or XP always a pain in the ass. I think those days are mostly over now though.
- shantly 7y agoIt used to be considered polite to append "(pdf warning)" to direct links to PDFs. I still like it, even though it's way less of a PITA now than it used to be.
- cesarb 7y agoPDFs are often big, which is a concern for those on metered connections.
- emddudley 7y ago> The Congressional Research Service (CRS), a federal legislative branch agency located within the Library of Congress, serves as shared staff exclusively to congressional committees and Members of Congress. CRS experts assist at every stage of the legislative process — from the early considerations that precede bill drafting, through committee hearings and floor debate, to the oversight of enacted laws and various agency activities. https://crsreports.congress.gov/Home/About https://crsreports.congress.gov/Home/About
- 60654 7y agoEncrypted DNS is a good idea, I just wish all of the basic protocols were getting encryption in-place, instead of being reinvented over HTTPS. First HTTP/3 (nee QUIC) reinvented TCP and ports over HTTPS, now DOH is reinventing DNS over HTTPS... Sigh. Both of these would be better off by evolving and modernizing their respective existing protocols. And HTTP is a client/server protocol with a _heavy_ handshake cost, why are we using it for a quick one-off request like DNS.
- iampims 7y agoin my experience, it's not about the protocols, it's about all existing middleboxes blocking/intercepting all traffic on non 443 ports. UDP traffic is notoriously blocked by routers. The only viable option being: HTTPS.
- sundbry 7y agoProbably because in your corporate/controlled environment you're supposed to use the company DNS for a good reason.
- bluejekyll 7y agoIf you're not using a VPN, DNS is actually pretty easily spoofed. DoH and DoT make that much harder.
- defanor 7y ago> The only viable option being: HTTPS. But why not DoT on port 443? The story about office workers, sysadmins, and service providers trying to make life harder for each other and complicating things for everyone seems unfortunate, but makes sense, yet I don't quite see why HTTP has to be involved.
- bluejekyll 7y agoHTTP2 isn't significantly more overhead than TLS in my experience. Also, using DoT over 443 would mean that you have an issue with traffic not being distinguishable for routing purposes at the edge. By making DNS on 443 DoH, it means that all HTTP2 routers/loadbalancers/etc. can work the same regardless of it being a Web request or a DNS request, because then they are both Web, i.e. HTTP, requests.
- totorovirus 7y agoFYI: South Korea uses SNI to block porn sites.
- baroffoos 7y agoEncrypted SNI is on the way. Alternatively, if the site is on a CDN or hosting platform you can usually send any SNI you want and it still resolves to the correct site.
- ameliaquining 7y agoMajor cloud providers started blocking domain fronting last year.
- darkhorn 7y agoFirefox users can enable ESNI from about:config. If the web site supports it then it will work.
- Glyptodon 7y agoMy only gripe with DNS over HTTPS is that it seems to somehow be coupled with making it harder for me to actually force everything to use a particular DNS at the OS level, so apps can do things like circumvent your pihole regardless of how you configure your device's DNS settings.
- baroffoos 7y agoThey could do that already. There is nothing requiring that your app uses the OS set dns server
- Glyptodon 7y agoI'm not a fan of apps doing that. I agree it's sort of tangential.
- Moru 7y agoBut your firewall could block port 53. If everything goes over https you can't do that any more either.
- baroffoos 7y agoThat is by design though. You want your dns requests to blend in with regular traffic on hostile networks / ISPs. The solution is to not have proprietary spyware devices in your network that don't let you set your own dns.
- unionpivo 7y agoSure, but they mostly didn't. Now we will have 2 mayor browsers, that might or might not resolve internal domains correctly. And unless you have AD, and ability to push to config clients, you will have to go to each and every computer and set it manually. And hope that updates wont break it further.
- lazylizard 7y agoWhy wont internal domains resolve correctly? Abc.private is 192.168.0.123 irregardless who's doing the name resolution n over which ports/protocols??
- ma2rten 7y agoDNS is heavily cached. What are the caching implications for encrypting DNS?
- TheSmiddy 7y agoIt's only the traffic that is encrypted. It's still cached on the server and the client.
- spc476 7y agoI wish it was cached by Firefox. But it's not. I'm running a DoH setup at home, and from the logs, it looks like Firefox is NOT doing any caching of results it gets. At least my DNS server is caching the results though.
- bluejekyll 7y agoIt's only the point-to-point transports that are encrypted, not the queries or responses, that is, the queries and responses are encrypted in transit but would still be cached in the clear for any other queries to benefit from on the resolvers. The caches will work the same as they do today.
- jedisct1 7y agoNot much any more, with load balancers/geo routing/CDNs generating ephemeral host names, and everybody using very low TTLs.
- ma2rten 7y agoThis was very well written. I am pleasantly surprised. Another concern is that DOH will complicate content delivery to users. Today, content delivery networks (CDNs) host multiple instances of web content on geographically dispersed servers. This creates resiliency for web services and helps to deliver content to users more quickly. If ISPs lose the ability to view users’ DNS queries, they will still be able to route users to a CDN, but not necessarily the closest or most efficient CDN. Technical measures that may alleviate this concern include sharing some user data (like general geolocation data) and CDN load management tactics. Is this a real concern? Don't ISPs just route on IP addresses? Other potential implications of DOH implementation involve issues such as international data flow and advertising competition. What on earth is this referring to?
- deleted 7y ago[deleted]
- doctorcroc 7y agoIt's referring to the ability of ISPs (as of last year) in the USA being able to use your DNS requests for advertising purposes. The argument for this is to expand competition around ad based products by enabling ISPs to join the game that large web properties currently dominate.
- StavrosK 7y agoGod forbid there's a piece of infrastructure that can't show ads.
- ascorbic 7y agoDNS lookups for CDNs will return a different (local) IP for clients in different regions. The proper way to handle this is using EDNS Client Subnet, which is what Google DOH does. CloudFlare DOH doesn't support this, but instead handles this by making the DNS request from a server near to the end user. This is only roughly accurate, and can't for example point a user's request to their ISP's on-prem edge cache: https://samknows.com/blog/dns-over-https-performance https://samknows.com/blog/dns-over-https-performance
- 7y ago
- pdkl95 7y agoBy its own definition[1], DOH forbids recursive resolution of queries. The client "MUST NOT use a different [DOH resolver] simply because it was discovered outside of the client's configuration"[2]. The protocol seems to be designed to require clients to send all of their DNS traffic to a single upstream provider. This may be similar to your current DNS configuration, and your network may even be limiting your ability to use the internet with bad policies on broken middleboxen. That's unfortunate for you, but please don't presume everyone has similar limitations. >> "But we need to overload port 443 to hide our DNS traffic!" It's unfortunate your ISP or national infrastructure requires such obfuscation. In those situations, the current DOH protocol could be a good workaround. However, protecting against a malicious upstream server sending bad results is very different than protecting against large institutions being able to eavesdrop on your DNS traffic to build a model of your pattern-of-life. The latter is only stopped by not giving a single entity all of your DNS traffic, which DOH explicitly requires. If you recursively resolve DNS queries locally - ideally in a future where traffic to authoritative servers is encrypted (DoT?) - only the first request goes to a centralized server. Most traffic goes to the domain's authoritative server, which is probably the same controlled by the same entity you are about to connect to with HTTPS. [1] https://news.ycombinator.com/item?id=21110296 https://news.ycombinator.com/item?id=21110296 [2] https://tools.ietf.org/html/rfc8484#section-3 https://tools.ietf.org/html/rfc8484#section-3
- ameliaquining 7y ago> Today, DNS queries are generally sent unencrypted. This allows any party between the browser and the resolver to discover which website users want to visit. Such parties can already monitor the IP address with which the browser is communicating, but monitoring DNS queries can identify which specific website users seek. As more services move to cloud computing infrastructure, this distinction becomes increasingly important, because multiple websites may be consolidated under a few IP addresses, rather than each having a unique IP address. This is super misleading. Even with DoH, any party on the network can see which websites you're talking to, because their hostnames are sent in the clear via SNI. ESNI fixes this, but it's not clear to me whether the major cloud providers are going to go for that, and if they don't it's not going anywhere. https://news.ycombinator.com/item?id=21264814 https://news.ycombinator.com/item?id=21264814 was a good discussion of the actual security benefits of DoH.
- colinprince 7y agoI wonder if Mozilla will change their rollout plan now that the UK has dropped their porn-filtering plans[0] 0. https://www.bbc.com/news/technology-50073102 https://www.bbc.com/news/technology-50073102
- ultraism 7y agoThey still will want to block piracy sites. https://en.wikipedia.org/wiki/List_of_websites_blocked_in_the_United_Kingdom#Court_ordered_implementations_targeting_copyright_and_trademark_infringement https://en.wikipedia.org/wiki/List_of_websites_blocked_in_th...
- LinuxBender 7y agoDisclaimer: This will be a wildly unpopular opinion. I do not believe that DoH was created first and foremost to protect the privacy of people. I believe that it was created to use the frog in boiling water methodology of silently pushing millions of people into centralized logged DNS that can be used for whatever purpose those companies see appropriate, in my personal opinion. I do not believe this opinion is far fetched. No company is going to just provide a large amount of infrastructure out of the kindness of their hearts. I am not saying that philanthropists do not exist. They do, but not here. This is a data grab first and foremost, in my opinion. Another factor in my opinion is the lack of support for a corporate infrastructure. Some companies may manage some facets of user settings in Chrome and Firefox via AD policies, but I believe that is the exception rather than the norm. Companies will be leaking even more internal infrastructure topology than they do today. It isn't like ISP's manage browser settings, nor would they want to. Nation states? DoH will not affect them at all. They will simply null route all of the DoH hosts like they do with existing proxies and VPN providers. This is what I had to do in my home network so that I could maintain control of my DNS.
- cracker_jacks 7y agoI think you're arguing against the wrong thing here. You want decentralization of DNS. I don't see DoH really impacting this issue in any clear direction. On one hand, you have centralized DNS (based on your ISP). DoH gives you some choice over that now through your browser. On the other, you have only a handful of DNS providers to choose from. DoH is just a technology, there's nothing preventing ISPs from still providing their DNS services over HTTPS.
- pdkl95 7y ago> I don't see DoH really impacting this issue in any clear direction. See my other posts[1][2] about why DoH explicitly requires centralization. > you have centralized DNS (based on your ISP) You might, I don't, because DNS doesn't require that the client delegate recursive resolution to an upstream server. [1] https://news.ycombinator.com/item?id=21110296 https://news.ycombinator.com/item?id=21110296 [2] https://news.ycombinator.com/item?id=21309811 https://news.ycombinator.com/item?id=21309811