3 ms·
Some would argue "still UDP based" is objectively worse, since it can be blocked. I don't think DNSCrypt is better for caching, doesn't it just protect one "le
by detaro 8y ago
Some would argue "still UDP based" is objectively worse, since it can be blocked.
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).
- gsich 8y agoMajor 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)
- icebraining 8y agoAre 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).
- michaelt 8y agoIn 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.
- detaro 8y agoProbably, yes. The key from that perspective is to have it in the same format as the content traffic.
- Arnavion 8y agoWe already have DNS over HTTP(S) now.
- svsucculents 8y agoWhat a mess.
- em-bee 8y agoblocking 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 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.