News for hackers. Stuff that matters.

A comment on DNS-over-HTTPS. Parent comment

Re:DNS-over-HTTPS by mseebach on Friday September 30, 2016 @04:57AM (#12611286)
It's an API that returns a document. Nothing fancy, no bells and whistles. If, for literally anything else, someone had suggested building such a service using raw sockets, they'd rightly be laughed out of the building.

Twilio isn't implemented using AT commands either, and for the same reason.

[ Parent | on HN ]
Re:DNS-over-HTTPS by chris_wot on Friday September 30, 2016 @06:10AM (#12611528)
What, resolving using a socket is now considered ridiculous?
[ Parent | on HN ]
Re:DNS-over-HTTPS by nothrabannosir on Friday September 30, 2016 @07:30AM (#12611818)
The comparison with Twilio is unfair.

DNS latency is an entire round trip added to every single fresh domain lookup you make. That's a lot of times, and we want those to be as fast as possible. At that point, the raw sockets vs full blown HTTP over TLS over TCP debate matters.

Twilio, on the other hand, is used in situations with comparably laughable latency requirements. At least two orders of magnitude.

Not saying it's doa, but the question has merit.

[ Parent | on HN ]