2 ms·
Most of the top comments in the thread are 1 years old now. DoH back then I think only have a Google DNS flavor which send request as human readable POST data
by yegle 7y ago
Most of the top comments in the thread are 1 years old now.
DoH back then I think only have a Google DNS flavor which send request as human readable POST data or query string and respond in JSON.
Since then the DoH has been standardized under RFC 8484 (not final yet) and switched to use DNS wire format.
DoT may have wider support right now due to 1) Android P have built-in support, and 2) Debian 10 uses subby as local DNS cache which send upstream request over DoT.
But I think DoH is catching up since Firefox and now Chrome are going to support it. I would assume Apple and Microsoft would follow along and add the DoH support to their browsers.
- dngray 7y ago> But I think DoH is catching up since Firefox and now Chrome are going to support it. I would assume Apple and Microsoft would follow along and add the DoH support to their browsers. I think DoHs will end up being the standard that 'wins' as such because DoT can be banned by governments who do not want you doing it. In addition to that I can see at some point DoHs becoming DNS over QUIC. It seems as if QUIC is now a part of HTTP/3 so that's quite likely. When the standards finalize: • https://datatracker.ietf.org/doc/draft-ietf-quic-transport/ https://datatracker.ietf.org/doc/draft-ietf-quic-transport/ • https://datatracker.ietf.org/doc/draft-huitema-quic-dnsoquic/ https://datatracker.ietf.org/doc/draft-huitema-quic-dnsoquic... What is interesting is DNSCrypt https://dnscrypt.info/faq https://dnscrypt.info/faq also acknowledge that fact under the section for DoHS: "Will automatically benefit from improvements made to HTTP/2 and, eventually, QUIC"