Re:The Big DNS Privacy Debate at FOSDEM
by em-bee on Thursday February 21, 2019 @08:58AM
(#19216873)
blocking or not blocking DNS is a two edged sword.
as we see in the discussion about the chromecast ultra: https://news.ycombinator.com/item?id=19170671 it is not necessarily desirable to have a way for apps to resolve DNS that can't be blocked at all.
Re:The Big DNS Privacy Debate at FOSDEM
by michaelt on Thursday February 07, 2019 @12:40PM
(#19106794)
In the internet of the future, DNS will move from UDP to TCP because it's better, and HTTP/3 will move from TCP to UDP because it's better.
Web 4.0 will consolidate these improvements, producing DNS over HTTP over QUIC over UDP.
Re:The Big DNS Privacy Debate at FOSDEM
by detaro on Thursday February 07, 2019 @12:46PM
(#19106843)
Probably, yes. The key from that perspective is to have it in the same format as the content traffic.
Re:The Big DNS Privacy Debate at FOSDEM
by Arnavion on Thursday February 07, 2019 @03:51PM
(#19108474)
We already have DNS over HTTP(S) now.
Re:The Big DNS Privacy Debate at FOSDEM
by svsucculents on Saturday February 09, 2019 @08:20AM
(#19122099)
What a mess.
Major advantage is the latency. TCP needs 3 trips, TLS an additional 4. With dnscrypt you have one request and one response.
Then again, Cloudflare and Quad9 terminate the connection almost instantly after finishing your request. Tested this with DoT though. (stubby with high timeout set)
Re:The Big DNS Privacy Debate at FOSDEM
by icebraining on Thursday February 07, 2019 @12:19PM
(#19106631)
Are you sure that's not a problem with the client? It seems Cloudflare supports leaving the connection open just fine (at least using the cloudflared client).
I don't think DNSCrypt is better for caching, doesn't it just protect one "leg" from a client (which can be a local cache) to a resolver (which also can be a cache) just like DoH? Similarly for pinning keys (although I think DNSCrypt made exchanging keys easier).