There is a new protocol from Google to do this: https://developers.google.com/speed/public-dns/docs/dns-over-https https://developers.google.com/speed/public-d

There is a new protocol from Google to do this: https://developers.google.com/speed/public-dns/docs/dns-over-https https://developers.google.com/speed/public-dns/docs/dns-over... The traditional reason that DNS doesn't use HTTP is (1) published DNS standards predate published HTTP standards by 9 years, and predate the mainstream popularity of the web by even more than that (so HTTP didn't even exist when DNS was created, nor was there any such thing as a firewall that only permitted HTTP traffic); (2) HTTP requires more roundtrips, which add more latency, while a UDP-based DNS connection can usually be answered in a single roundtrip. However, Google has pointed out that their DNS-over-HTTPS approach can improve security and privacy. Presumably it will inherently be slightly higher latency because you need a couple of roundtrips for the TCP and TLS setup even before you can send a query.