Comparing the Effects of DNS, DoT, and DoH on Web Performance
Austin Hounsel, Kevin Borgolte, Paul Schmitt, Jordan Holland, Nick, Feamster
TL;DR
This study compares the impact of traditional DNS, DoT, and DoH protocols on web performance, revealing trade-offs between privacy, response times, and page load efficiency across different network conditions.
Contribution
It provides empirical measurements of DNS protocols' effects on web performance and offers optimization recommendations for better user experience.
Findings
DoH and DoT have higher response times than Do53.
Page load times can be better with DoH and DoT under certain conditions.
Traditional DNS (Do53) loads pages fastest when throughput is low or packet loss is high.
Abstract
Nearly every service on the Internet relies on the Domain Name System (DNS), which translates a human-readable name to an IP address before two endpoints can communicate. Today, DNS traffic is unencrypted, leaving users vulnerable to eavesdropping and tampering. Past work has demonstrated that DNS queries can reveal a user's browsing history and even what smart devices they are using at home. In response to these privacy concerns, two new protocols have been proposed: DNS-over-HTTPS (DoH) and DNS-over-TLS (DoT). Instead of sending DNS queries and responses in the clear, DoH and DoT establish encrypted connections between users and resolvers. By doing so, these protocols provide privacy and security guarantees that traditional DNS (Do53) lacks. In this paper, we measure the effect of Do53, DoT, and DoH on query response times and page load times from five global vantage points. We find…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
Comparing the Effects of DNS, DoT, and DoH
on Web Performance
Austin Hounsel
\institutionPrinceton University
Kevin Borgolte
\institutionPrinceton University
Paul Schmitt
\institutionPrinceton University
Jordan Holland
\institutionPrinceton University
Nick Feamster
\institutionUniversity of Chicago
\balance
The reference list from the paper itself. Each links out to its DOI / PubMed record.
- 1[1] Amazon “Amazon EC 2 Instance Types”, 2019 URL: https://aws.amazon.com/ec 2/instance-types
- 2[2] Mike Belshe, Roberto Peon and Martin Thomson “Hypertext Transfer Protocol Version 2 (HTTP/2)” (Proposed Standard), Internet Requests for Comments 7540 RFC Editor, Internet Requests for Comments, 2015 Internet Engineering Task Force URL: http://www.ietf.org/rfc/rfc 7540.txt
- 3[3] Daniel J. Bernstein “DNS Curve: Usable Security for DNS”, 2009 URL: https://dnscurve.org/
- 4[4] Stephane Bortzmeyer “DNS Privacy Considerations” (Informational), Internet Requests for Comments 7626 RFC Editor, Internet Requests for Comments, 2015 Internet Engineering Task Force URL: http://www.ietf.org/rfc/rfc 7626.txt
- 5[5] Timm Böttger, Felix Cuadrado, Gianni Antichi, Eder Leao Fernandes, Gareth Tyson, Ignacio Castro and Steve Uhlig “An Empirical Study of the Cost of DNS-over-HTTPS” In Proceedings of the 2019 Internet Measurement Conference (IMC) Amsterdam, Netherlands: Association for Computing Machinery (ACM), 2019 DOI: 10.1145/3355369.3355575 · doi ↗
- 6[6] Michael Butkiewicz, Harsha V Madhyastha and Vyas Sekar “Understanding website complexity: measurements, metrics, and implications” In Proceedings of the 11th ACM SIGCOMM Conference on Internet Measurement (IMC) Berlin, Germany: Association for Computing Machinery (ACM), 2011 URL: https://web.eecs.umich.edu/~harshavm/papers/imc 11.pdf
- 7[7] Cloudflare “The Nitty Gritty – Cloudflare Resolver”, 2019 URL: https://developers.cloudflare.com/1.1.1.1/nitty-gritty-details/
- 8[8] Cloudflare “What is 1.1.1.1?”, 2019 URL: https://www.cloudflare.com/learning/dns/what-is-1.1.1.1/