T-DNS: Connection-Oriented DNS to Improve Privacy and Security

T-DNS: Connection-Oriented DNS to Improve Privacy and Security

Heidemann, John
USC/Information Sciences Institute

John Heidemann 2014. T-DNS: Connection-Oriented DNS to Improve Privacy and Security. Presentation at the Spring DNS-OARC Meeting.

Abstract

This talk will discuss \emphconnection-oriented DNS to improve DNS security and privacy. DNS is the canonical example of a connectionless, single packet, request/response protocol, with UDP as its dominant transport. Yet DNS today is challenged by eavesdropping that compromises privacy, source-address spoofing that results in denial-of-service (DoS) attacks on the server and third parties, injection attacks that exploit fragmentation, and size limitations that constrain policy and operational choices. We propose \empht-DNS to address these problems: it uses TCP to smoothly support large payloads and mitigate spoofing and amplification for DoS. T-DNS uses transport-layer security (TLS) to provide privacy from users to their DNS resolvers and optionally to authoritative servers. \newline \indent Traditional wisdom is that connection setup will balloon latency for clients and overwhelm servers. We provide data to show that these assumptions are overblown—our model of end-to-end latency shows \emphTLS to the recursive resolver is only about 5–24% slower, with UDP to the authoritative server. End-to-end latency is 19–33% slower with TLS to recursive and TCP to authoritative. Experiments behind these models show that after connection establishment, TCP and TLS latency is equivalent to UDP. Using diverse trace data we show that frequent connection reuse is possible (60–95% for stub and recursive resolvers, although half that for authoritative servers). With conservative timeouts (20 s at authoritative servers and 60 s elsewhere) we show that \emphserver memory requirements match current hardware: a large recursive resolver may have 25k active connections consuming about 9 GB of RAM. These results depend on specific design and implementation decisions—query pipelining, out-of-order responses, TLS connection resumption, and plausible timeouts. \newline \indent We hope to solicit feedback from the OARC community about this work to understand design and operational concerns if T-DNS deployment was widespread. The work in the talk is by Liang Zhu, Zi Hu, and John Heidemann (all of USC/ISI), Duane Wessels and Allison Mankin (both of Verisign), and Nikita Somaiya (USC/ISI). \newline \indent A technical report describing the work is at \urlhttp://www.isi.edu/%7ejohnh/PAPERS/Zhu14a.pdf and the protocol changes are described as \urlhttp://datatracker.ietf.org/doc/draft-hzhwm-start-tls-for-dns/.

Reference

@misc{Heidemann14c,
  author = {Heidemann, John},
  title = {T-DNS: Connection-Oriented {DNS} to Improve Privacy and Security},
  howpublished = {Presentation at the Spring DNS-OARC Meeting},
  month = may,
  year = {2014},
  sortdate = {2014-05-01},
  project = {ant, lacrend, tdns},
  jsubject = {dns},
  location = {johnh: pafile},
  keywords = {based on [Zhu14a]},
  note = {This talk is about the technical report
                    ISI-TR-2014-688, joint work with Liang Zhu, Zi Hu,
                    duane Wessels, Allison Mankin, and Nikita Somaiya},
  url = {http://www.isi.edu/%7ejohnh/PAPERS/Heidemann14c.html},
  pdfurl = {http://www.isi.edu/%7ejohnh/PAPERS/Heidemann14c.pdf},
  myorganization = {USC/Information Sciences Institute},
  copyrightholder = {authors},
  blogurl = {https://ant.isi.edu/blog/?p=491}
}