News for hackers. Stuff that matters.
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by elcomet on Saturday September 07, 2019 @04:17AM (#20902513)
Why don't they rather include a resolver in Firefox ?

This way, no privacy problems, you're directly contacting authoritarive servers. And you don't rely on a single dns-over-https provider.

Is the latency a big problem there? I would say that with caching it is not too bad.

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by hannob on Saturday September 07, 2019 @04:42AM (#20902596)
1. The connection to the authoritative servers isn't encrypted, so the whole point of DoH is undermined.

2. There's plenty of networks that don't let arbitrary DNS traffic out, so this doesn't work without another fallbacks. Fallbacks for security features are bad.

I see that there are legit controversies around DoH. But these "Why don't you just do X?" comments aren't helpful. Try to understand the problem they're trying to resolve.

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by EvanAnderson on Saturday September 07, 2019 @04:58AM (#20902651)
I disagree that the OP's comment isn't helpful. Mozilla could have taken a tack that would have increased decentralization and promoted privacy (DNS-over-TLS exists). Instead, they went the way of a centralized protocol that just trades one set of potentially bad actors (ISPs) for another.

re: network policy - If you're paying to use a network with policy that you disagree with vote w/ your wallet. If you're using somebody else's network (i.e. a corporate network I'm paid to administer, for example) it's reasonable to accept that you're bound by the owner's policy-- it's their network.

Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by mtsr on Saturday September 07, 2019 @06:06AM (#20902865)
I’d love to use DoT, but afaik it’s currently mostly only supported by DNS resolvers (Google, CloudFlare and other privacy-exploiting companies) rather than authoritative DNS servers.
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by elcomet on Saturday September 07, 2019 @04:52AM (#20902629)
Well I'm asking because I'm trying to understand the drawbacks of a resolving server. Thanks for the explanation !
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by EvanAnderson on Saturday September 07, 2019 @04:40AM (#20902585)
A local resolver using root hints and DNS-over-TLS would be a win for privacy and, at the same time, would not promote centralization of the Internet to DNS-over-HTTPS providers. It still suffers from the problem of overriding local network policy but it's better than just handing all the queries over to a single DoH provider.
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by StavrosK on Saturday September 07, 2019 @11:46AM (#20904490)
How is DoT different from DoH? Do you have an issue with the format on the wire? Because otherwise you can use whichever resolver you want in either case.
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by EvanAnderson on Saturday September 07, 2019 @01:28PM (#20905216)
I'm on mobile so rather than restate I'll just refer to a comment w/ a good link from an earlier discussion: https://news.ycombinator.com/item?id=19624136
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by poizan42 on Saturday September 07, 2019 @04:53AM (#20902634)
Besides what the other commenters have said, it also just seems like a bad idea to add 170 million extra recursive resolvers, I don't know how well the dns infrastructure would cope with that extra amount of traffic.
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default by mtsr on Saturday September 07, 2019 @06:09AM (#20902872)
Each of which individually generates really limited traffic?

Besides, the number of domains and relatively short TTLs mean that even the big resolvers will not have most requests cached except for the most popular domains.