> Every response is return asynchronously, we can achieve nonblocking.
same goes for UDP which DNS runs over normally.
Like the original commenter, I fail to see how stacking DNS over HTTP over TLS over TCP over IP is going to be faster than running DNS over UDP over IP.
Also, you still need to resolve the address of your DNS-over-HTTP server, which you'd probably still do over traditional DNS-over-UDP.
This feels like doing nothing but adding complexity for zero gain.
Zero gain except going from easy eavesdropping, blocking, censoring, etc. to effectively unblockable, private and secure? Ok.
Also you would probably need to put in the IP of the DNS server manually, exactly like you have to with DNS now.
I would love to know how widely used UDP over TLS is in the wild.
Not quite the same, but QUIC is close to this description description, so it might be higher than initially expected?
From 2016: https://www.bizety.com/2016/01/26/half-of-chrome-to-google-t...
Re:DNS over HTTPS
by sapphire_tomb on Wednesday January 17, 2018 @03:58AM
(#16166498)
From what I understand the "cURL" format of the word is popular mostly with users of the PHP bindings. "curl" is what the project uses, but I'm not sure they really care what other people refer to it as :)
Re:DNS over HTTPS
by sohkamyung on Wednesday January 17, 2018 @04:12AM
(#16166565)
I think it depends on whether you are referring to the project or the executable [1]: "cURL is the name of the project."
If your question is how to reuse the connection pool for, say, 1000 DNS queries from one machine, curl already uses a connection pool. Next, to use fewer TCP connections and get faster response, my first proposal is HTTP/2 which supports TCP multiplexing such that multiple requests can be issued over a single TCP connection. Every response is return asynchronously, we can achieve nonblocking.
cURL also supports HTTP/2.
Speaking of word: it seems author of curl project prefers “curl” over “cURL”? Worth asking.