Old but Gold: Prospecting TCP to Engineer DNS Anycast (extended). Moura, G. C. M., Heidemann, J., Hardaker, W., Bulten, J., Ceron, J., & Hesselman, C. Technical Report ISI-TR-739b, USC/Information Sciences Institute, June, 2020. Released June 2020, updated April 2021![Old but Gold: Prospecting TCP to Engineer DNS Anycast (extended) [link]](https://bibbase.org/img/filetypes/link.svg "link")
Paper abstract bibtex DNS latency is a concern for many service operators: CDNs exist to reduce service latency to end-users, but must rely on global DNS for reachability and load-balancing. We show that a recursive DNS resolver's preference for low latency shifts traffic at TLDs and the DNS root. DNS latency today is monitored with distributed infrastructure such as RIPE Atlas, or with active probing using Verfploeter. While Atlas coverage is wide, it is incomplete, and Verfploeter coverage in IPv6 is limited. In this paper we show that \emphpassive observation of TCP handshakes provides a mechanism to measure DNS latency. Passive RTT estimation from TCP is an old idea, but it has never been used to examine DNS before. We show that there is sufficient TCP DNS traffic today to provide greater coverage than existing approaches, and is the best method to observe latency of DNS using IPv6. We show that estimates of DNS latency from TCP is consistent with UDP latency. Our approach finds real problems: We define \emphDNS polarization, a new problem where a hypergiant sends global traffic to one anycast site rather than taking advantage of the global anycast deployment—we found Google traffic polarized and cut its latency from 100ms to 10ms, and for Microsoft, the latency cut due to traffic being depolarized was from 90ms to 20ms. Our approach is in operational use for a European country's top-level domain, and monitoring with our tool helped find and correct a routing detour sending European traffic to Australia.
@TechReport{Moura20a,
author = "Giovane C. M. Moura and John Heidemann and
Wes Hardaker and Jeroen Bulten and Joao Ceron
and Christian Hesselman",
title = "Old but Gold: Prospecting {TCP} to Engineer {DNS} Anycast (extended)",
institution = "USC/Information Sciences Institute",
year = 2020,
month = jun,
sortdate = "2020-06-30",
project = "ant, lacanic, paaddos, ddidd, diiner",
jsubject = "network_security",
number = "ISI-TR-739b",
note = "Released June 2020, updated April 2021",
jlocation = "johnh: pafile",
keywords = "anycast, dns, tcp, latency, root, .nl-tld",
url = "https://ant.isi.edu/%7ejohnh/PAPERS/Moura20a.html",
pdfurl = "https://ant.isi.edu/%7ejohnh/PAPERS/Moura20a.pdf",
otherurl = "https://www.isi.edu/publications/trpublic/pdfs/isi-tr-739.pdf",
dataurl = "https://ant.isi.edu/datasets/dns/#Moura20a_data",
myorganization = "USC/Information Sciences Institute",
copyrightholder = "authors",
abstract = "
DNS latency is a concern for many service operators: CDNs exist to
reduce service latency to end-users, but must rely on global DNS for
reachability and load-balancing. We show that a recursive DNS
resolver's preference for low latency shifts traffic at TLDs and the
DNS root. DNS latency today is monitored with distributed
infrastructure such as RIPE Atlas, or with active probing using
Verfploeter. While Atlas coverage is wide, it is incomplete, and
Verfploeter coverage in IPv6 is limited. In this paper we show that
\emph{passive observation of TCP handshakes provides a mechanism to
measure DNS latency}. Passive RTT estimation from TCP is an old idea,
but it has never been used to examine DNS before. We show that there
is sufficient TCP DNS traffic today to provide greater coverage than
existing approaches, and is the best method to observe latency of DNS
using IPv6. We show that estimates of DNS latency from TCP is
consistent with UDP latency. Our approach finds real problems: We
define \emph{DNS polarization}, a new problem where a hypergiant sends
global traffic to one anycast site rather than taking advantage of the
global anycast deployment---we found Google traffic polarized and cut
its latency from 100ms to 10ms, and for Microsoft, the latency cut due
to traffic being depolarized was from 90ms to 20ms. Our approach is
in operational use for a European country's top-level domain, and
monitoring with our tool helped find and correct a routing detour
sending European traffic to Australia.
",
}
Downloads: 0
{"_id":"Jb2SxGQo53a7QcWbs","bibbaseid":"moura-heidemann-hardaker-bulten-ceron-hesselman-oldbutgoldprospectingtcptoengineerdnsanycastextended-2020","author_short":["Moura, G. C. M.","Heidemann, J.","Hardaker, W.","Bulten, J.","Ceron, J.","Hesselman, C."],"bibdata":{"bibtype":"techreport","type":"techreport","author":[{"firstnames":["Giovane","C.","M."],"propositions":[],"lastnames":["Moura"],"suffixes":[]},{"firstnames":["John"],"propositions":[],"lastnames":["Heidemann"],"suffixes":[]},{"firstnames":["Wes"],"propositions":[],"lastnames":["Hardaker"],"suffixes":[]},{"firstnames":["Jeroen"],"propositions":[],"lastnames":["Bulten"],"suffixes":[]},{"firstnames":["Joao"],"propositions":[],"lastnames":["Ceron"],"suffixes":[]},{"firstnames":["Christian"],"propositions":[],"lastnames":["Hesselman"],"suffixes":[]}],"title":"Old but Gold: Prospecting TCP to Engineer DNS Anycast (extended)","institution":"USC/Information Sciences Institute","year":"2020","month":"June","sortdate":"2020-06-30","project":"ant, lacanic, paaddos, ddidd, diiner","jsubject":"network_security","number":"ISI-TR-739b","note":"Released June 2020, updated April 2021","jlocation":"johnh: pafile","keywords":"anycast, dns, tcp, latency, root, .nl-tld","url":"https://ant.isi.edu/%7ejohnh/PAPERS/Moura20a.html","pdfurl":"https://ant.isi.edu/%7ejohnh/PAPERS/Moura20a.pdf","otherurl":"https://www.isi.edu/publications/trpublic/pdfs/isi-tr-739.pdf","dataurl":"https://ant.isi.edu/datasets/dns/#Moura20a_data","myorganization":"USC/Information Sciences Institute","copyrightholder":"authors","abstract":"DNS latency is a concern for many service operators: CDNs exist to reduce service latency to end-users, but must rely on global DNS for reachability and load-balancing. We show that a recursive DNS resolver's preference for low latency shifts traffic at TLDs and the DNS root. DNS latency today is monitored with distributed infrastructure such as RIPE Atlas, or with active probing using Verfploeter. While Atlas coverage is wide, it is incomplete, and Verfploeter coverage in IPv6 is limited. In this paper we show that \\emphpassive observation of TCP handshakes provides a mechanism to measure DNS latency. Passive RTT estimation from TCP is an old idea, but it has never been used to examine DNS before. We show that there is sufficient TCP DNS traffic today to provide greater coverage than existing approaches, and is the best method to observe latency of DNS using IPv6. We show that estimates of DNS latency from TCP is consistent with UDP latency. Our approach finds real problems: We define \\emphDNS polarization, a new problem where a hypergiant sends global traffic to one anycast site rather than taking advantage of the global anycast deployment—we found Google traffic polarized and cut its latency from 100ms to 10ms, and for Microsoft, the latency cut due to traffic being depolarized was from 90ms to 20ms. Our approach is in operational use for a European country's top-level domain, and monitoring with our tool helped find and correct a routing detour sending European traffic to Australia. ","bibtex":"@TechReport{Moura20a,\n\tauthor = \t\"Giovane C. M. Moura and John Heidemann and\n \t\tWes Hardaker and Jeroen Bulten and Joao Ceron\n and Christian Hesselman\",\n\ttitle = \t\"Old but Gold: Prospecting {TCP} to Engineer {DNS} Anycast (extended)\",\n\tinstitution = \t\"USC/Information Sciences Institute\",\n\tyear = \t\t2020,\n\tmonth = \tjun,\n\tsortdate = \"2020-06-30\",\n\tproject = \"ant, lacanic, paaddos, ddidd, diiner\",\n\tjsubject = \"network_security\",\n\tnumber = \t\"ISI-TR-739b\",\n\tnote = \"Released June 2020, updated April 2021\",\n\tjlocation = \t\"johnh: pafile\",\n\tkeywords = \t\"anycast, dns, tcp, latency, root, .nl-tld\",\n\turl =\t\t\"https://ant.isi.edu/%7ejohnh/PAPERS/Moura20a.html\",\n\tpdfurl =\t\"https://ant.isi.edu/%7ejohnh/PAPERS/Moura20a.pdf\",\n\totherurl = \"https://www.isi.edu/publications/trpublic/pdfs/isi-tr-739.pdf\",\n\tdataurl =\t\"https://ant.isi.edu/datasets/dns/#Moura20a_data\",\n\tmyorganization =\t\"USC/Information Sciences Institute\",\n\tcopyrightholder = \"authors\",\n\tabstract = \"\nDNS latency is a concern for many service operators: CDNs exist to\nreduce service latency to end-users, but must rely on global DNS for\nreachability and load-balancing. We show that a recursive DNS\nresolver's preference for low latency shifts traffic at TLDs and the\nDNS root. DNS latency today is monitored with distributed\ninfrastructure such as RIPE Atlas, or with active probing using\nVerfploeter. While Atlas coverage is wide, it is incomplete, and\nVerfploeter coverage in IPv6 is limited. In this paper we show that\n\\emph{passive observation of TCP handshakes provides a mechanism to\nmeasure DNS latency}. Passive RTT estimation from TCP is an old idea,\nbut it has never been used to examine DNS before. We show that there\nis sufficient TCP DNS traffic today to provide greater coverage than\nexisting approaches, and is the best method to observe latency of DNS\nusing IPv6. We show that estimates of DNS latency from TCP is\nconsistent with UDP latency. Our approach finds real problems: We\ndefine \\emph{DNS polarization}, a new problem where a hypergiant sends\nglobal traffic to one anycast site rather than taking advantage of the\nglobal anycast deployment---we found Google traffic polarized and cut\nits latency from 100ms to 10ms, and for Microsoft, the latency cut due\nto traffic being depolarized was from 90ms to 20ms. Our approach is\nin operational use for a European country's top-level domain, and\nmonitoring with our tool helped find and correct a routing detour\nsending European traffic to Australia.\n\",\n}\n\n","author_short":["Moura, G. C. M.","Heidemann, J.","Hardaker, W.","Bulten, J.","Ceron, J.","Hesselman, C."],"bibbaseid":"moura-heidemann-hardaker-bulten-ceron-hesselman-oldbutgoldprospectingtcptoengineerdnsanycastextended-2020","role":"author","urls":{"Paper":"https://ant.isi.edu/%7ejohnh/PAPERS/Moura20a.html"},"keyword":["anycast","dns","tcp","latency","root",".nl-tld"],"metadata":{"authorlinks":{}}},"bibtype":"techreport","biburl":"https://bibbase.org/f/dHevizJoWEhWowz8q/johnh-2023-2.bib","dataSources":["YLyu3mj3xsBeoqiHK","fLZcDgNSoSuatv6aX","fxEParwu2ZfurScPY","7nuQvtHTqKrLmgu99"],"keywords":["anycast","dns","tcp","latency","root",".nl-tld"],"search_terms":["old","gold","prospecting","tcp","engineer","dns","anycast","extended","moura","heidemann","hardaker","bulten","ceron","hesselman"],"title":"Old but Gold: Prospecting TCP to Engineer DNS Anycast (extended)","year":2020}