@TechReport{Moura19a,
	author = 	"Giovane C. M. Moura and John Heidemann and
        		Ricardo de O. Schmidt and Wes Hardaker",
	title = 	"Cache Me If You Can: Effects of {DNS} {Time-to-Live} (extended)",
	institution = 	"USC/Information Sciences Institute",
	year = 		2019,
	sortdate = "2018-07-16",
	number = 	"ISI-TR-734b",
	note = "Released May 2018, updated Sept.~2019",
	project = "ant, lacanic, divoice, paaddos, nipet, ddidd",
	jsubject = "network_security",
	month = 	jul,
	jlocation = 	"johnh: pafile",
	keywords = 	"anycast, dns, ttl, ddos, root ddos",
	url =		"https://ant.isi.edu/%7ejohnh/PAPERS/Moura19a.html",
	pdfurl =	"https://ant.isi.edu/%7ejohnh/PAPERS/Moura19a.pdf",
	xxxblogurl = "https://ant.isi.edu/blog/?p=1192",
	otherurl = "ftp://ftp.isi.edu/isi-pubs/tr-734.pdf",
	dataurl =	"https://ant.isi.edu/datasets/dns/#Moura19a_data",
	myorganization =	"USC/Information Sciences Institute",
	copyrightholder = "authors",
	abstract = "
DNS depends on extensive caching for good performance, and every DNS
zone owner must set Time-to-Live (TTL) values to control their
DNS caching.  Today there is relatively little guidance backed by
research about how to set TTLs, and operators must balance conflicting
demands of caching against agility of configuration.  Exactly how TTL
value choices affect operational networks is quite challenging to
understand for several reasons:  DNS is a distributed service, DNS
resolution is security-sensitive, and resolvers require multiple types
of information as they traverse the DNS hierarchy.  These complications
mean there are multiple frequently interacting, places TTLs can be
specified.  This paper provides the first careful evaluation of how
these factors affect the effective cache lifetimes of DNS records, and
provides recommendations for how to configure DNS TTLs based on our
findings.  We provide recommendations in TTL choice for different
situations, and for where they must be configured.  We show that longer
TTLs have significant promise, reducing median latency from 183ms to
28.7ms for one country-code TLD.
",
}

{"_id":"GXTMW3yarDuikzQJp","bibbaseid":"moura-heidemann-deoschmidt-hardaker-cachemeifyoucaneffectsofdnstimetoliveextended-2019","author_short":["Moura, G. C. M.","Heidemann, J.","de O. Schmidt, R.","Hardaker, W."],"bibdata":{"bibtype":"techreport","type":"techreport","author":[{"firstnames":["Giovane","C.","M."],"propositions":[],"lastnames":["Moura"],"suffixes":[]},{"firstnames":["John"],"propositions":[],"lastnames":["Heidemann"],"suffixes":[]},{"firstnames":["Ricardo"],"propositions":["de"],"lastnames":["O.","Schmidt"],"suffixes":[]},{"firstnames":["Wes"],"propositions":[],"lastnames":["Hardaker"],"suffixes":[]}],"title":"Cache Me If You Can: Effects of DNS Time-to-Live (extended)","institution":"USC/Information Sciences Institute","year":"2019","sortdate":"2018-07-16","number":"ISI-TR-734b","note":"Released May 2018, updated Sept. 2019","project":"ant, lacanic, divoice, paaddos, nipet, ddidd","jsubject":"network_security","month":"July","jlocation":"johnh: pafile","keywords":"anycast, dns, ttl, ddos, root ddos","url":"https://ant.isi.edu/%7ejohnh/PAPERS/Moura19a.html","pdfurl":"https://ant.isi.edu/%7ejohnh/PAPERS/Moura19a.pdf","xxxblogurl":"https://ant.isi.edu/blog/?p=1192","otherurl":"ftp://ftp.isi.edu/isi-pubs/tr-734.pdf","dataurl":"https://ant.isi.edu/datasets/dns/#Moura19a_data","myorganization":"USC/Information Sciences Institute","copyrightholder":"authors","abstract":"DNS depends on extensive caching for good performance, and every DNS zone owner must set Time-to-Live (TTL) values to control their DNS caching. Today there is relatively little guidance backed by research about how to set TTLs, and operators must balance conflicting demands of caching against agility of configuration. Exactly how TTL value choices affect operational networks is quite challenging to understand for several reasons: DNS is a distributed service, DNS resolution is security-sensitive, and resolvers require multiple types of information as they traverse the DNS hierarchy. These complications mean there are multiple frequently interacting, places TTLs can be specified. This paper provides the first careful evaluation of how these factors affect the effective cache lifetimes of DNS records, and provides recommendations for how to configure DNS TTLs based on our findings. We provide recommendations in TTL choice for different situations, and for where they must be configured. We show that longer TTLs have significant promise, reducing median latency from 183ms to 28.7ms for one country-code TLD. ","bibtex":"@TechReport{Moura19a,\n\tauthor = \t\"Giovane C. M. Moura and John Heidemann and\n \t\tRicardo de O. Schmidt and Wes Hardaker\",\n\ttitle = \t\"Cache Me If You Can: Effects of {DNS} {Time-to-Live} (extended)\",\n\tinstitution = \t\"USC/Information Sciences Institute\",\n\tyear = \t\t2019,\n\tsortdate = \"2018-07-16\",\n\tnumber = \t\"ISI-TR-734b\",\n\tnote = \"Released May 2018, updated Sept.~2019\",\n\tproject = \"ant, lacanic, divoice, paaddos, nipet, ddidd\",\n\tjsubject = \"network_security\",\n\tmonth = \tjul,\n\tjlocation = \t\"johnh: pafile\",\n\tkeywords = \t\"anycast, dns, ttl, ddos, root ddos\",\n\turl =\t\t\"https://ant.isi.edu/%7ejohnh/PAPERS/Moura19a.html\",\n\tpdfurl =\t\"https://ant.isi.edu/%7ejohnh/PAPERS/Moura19a.pdf\",\n\txxxblogurl = \"https://ant.isi.edu/blog/?p=1192\",\n\totherurl = \"ftp://ftp.isi.edu/isi-pubs/tr-734.pdf\",\n\tdataurl =\t\"https://ant.isi.edu/datasets/dns/#Moura19a_data\",\n\tmyorganization =\t\"USC/Information Sciences Institute\",\n\tcopyrightholder = \"authors\",\n\tabstract = \"\nDNS depends on extensive caching for good performance, and every DNS\nzone owner must set Time-to-Live (TTL) values to control their\nDNS caching. Today there is relatively little guidance backed by\nresearch about how to set TTLs, and operators must balance conflicting\ndemands of caching against agility of configuration. Exactly how TTL\nvalue choices affect operational networks is quite challenging to\nunderstand for several reasons: DNS is a distributed service, DNS\nresolution is security-sensitive, and resolvers require multiple types\nof information as they traverse the DNS hierarchy. These complications\nmean there are multiple frequently interacting, places TTLs can be\nspecified. This paper provides the first careful evaluation of how\nthese factors affect the effective cache lifetimes of DNS records, and\nprovides recommendations for how to configure DNS TTLs based on our\nfindings. We provide recommendations in TTL choice for different\nsituations, and for where they must be configured. We show that longer\nTTLs have significant promise, reducing median latency from 183ms to\n28.7ms for one country-code TLD.\n\",\n}\n\n","author_short":["Moura, G. C. M.","Heidemann, J.","de O. Schmidt, R.","Hardaker, W."],"bibbaseid":"moura-heidemann-deoschmidt-hardaker-cachemeifyoucaneffectsofdnstimetoliveextended-2019","role":"author","urls":{"Paper":"https://ant.isi.edu/%7ejohnh/PAPERS/Moura19a.html"},"keyword":["anycast","dns","ttl","ddos","root ddos"],"metadata":{"authorlinks":{}}},"bibtype":"techreport","biburl":"https://bibbase.org/f/dHevizJoWEhWowz8q/johnh-2023-2.bib","dataSources":["YLyu3mj3xsBeoqiHK","fLZcDgNSoSuatv6aX","fxEParwu2ZfurScPY","7nuQvtHTqKrLmgu99"],"keywords":["anycast","dns","ttl","ddos","root ddos"],"search_terms":["cache","effects","dns","time","live","extended","moura","heidemann","de o. schmidt","hardaker"],"title":"Cache Me If You Can: Effects of DNS Time-to-Live (extended)","year":2019}