@TechReport{Mueller17a,
        author =        {Moritz M\"{u}ller and Giovane C. M. Moura and
 Ricardo de O. Schmidt and John Heidemann},
 title = "Recursives in the Wild: Engineering Authoritative {DNS} Servers",
	institution = "USC/Information Sciences Institute",
	year = 		2017,
	sortdate = 		"2017-06-02", 
	project = "ant, lacrend, retrofuturebridge",
	jsubject = "routing",
	number =	"ISI-TR-720",
	month =		jun,
	jlocation =	"johnh: pafile",
	keywords =	"anycast, recursive DNS, authoritative selection",
	url =		"https://ant.isi.edu/%7ejohnh/PAPERS/Mueller17a.html",
	pdfurl =	"https://ant.isi.edu/%7ejohnh/PAPERS/Mueller17a.pdf",
	myorganization =	"USC/Information Sciences Institute",
	copyrightholder = "authors",
	abstract = "In Internet Domain Name System (DNS), services 
operate \emph{authoritative} name servers that individuals query 
through \emph{recursive resolvers}.  Operators strive to provide reliability
by operating multiple name servers (NS), each on a separate IP
address, and by using IP anycast to allow NSes to provide service from
many physical locations.  To meet their goals of minimizing latency
and balancing load across NSes and anycast, operators need to know how
recursive resolvers select an NS, and how that interacts with their NS
deployments.  Prior work has shown some recursives search for low
latency, while others pick an NS at random or round robin, but did not
examine how prevalent each choice was.  This paper provides the first
analysis of how recursives select between name servers in the wild,
and from that we provide guidance to name server operators to reach
their goals.  We conclude that all NSes need to be equally strong and
therefore we recommend to deploy IP anycast at every single
authoritative.",
}

{"_id":"ABTvRkZqfqFuPfm25","bibbaseid":"mller-moura-deoschmidt-heidemann-recursivesinthewildengineeringauthoritativednsservers-2017","author_short":["Müller, M.","Moura, G. C. M.","de O. Schmidt, R.","Heidemann, J."],"bibdata":{"bibtype":"techreport","type":"techreport","author":[{"firstnames":["Moritz"],"propositions":[],"lastnames":["Müller"],"suffixes":[]},{"firstnames":["Giovane","C.","M."],"propositions":[],"lastnames":["Moura"],"suffixes":[]},{"firstnames":["Ricardo"],"propositions":["de"],"lastnames":["O.","Schmidt"],"suffixes":[]},{"firstnames":["John"],"propositions":[],"lastnames":["Heidemann"],"suffixes":[]}],"title":"Recursives in the Wild: Engineering Authoritative DNS Servers","institution":"USC/Information Sciences Institute","year":"2017","sortdate":"2017-06-02","project":"ant, lacrend, retrofuturebridge","jsubject":"routing","number":"ISI-TR-720","month":"June","jlocation":"johnh: pafile","keywords":"anycast, recursive DNS, authoritative selection","url":"https://ant.isi.edu/%7ejohnh/PAPERS/Mueller17a.html","pdfurl":"https://ant.isi.edu/%7ejohnh/PAPERS/Mueller17a.pdf","myorganization":"USC/Information Sciences Institute","copyrightholder":"authors","abstract":"In Internet Domain Name System (DNS), services operate \\emphauthoritative name servers that individuals query through \\emphrecursive resolvers. Operators strive to provide reliability by operating multiple name servers (NS), each on a separate IP address, and by using IP anycast to allow NSes to provide service from many physical locations. To meet their goals of minimizing latency and balancing load across NSes and anycast, operators need to know how recursive resolvers select an NS, and how that interacts with their NS deployments. Prior work has shown some recursives search for low latency, while others pick an NS at random or round robin, but did not examine how prevalent each choice was. This paper provides the first analysis of how recursives select between name servers in the wild, and from that we provide guidance to name server operators to reach their goals. We conclude that all NSes need to be equally strong and therefore we recommend to deploy IP anycast at every single authoritative.","bibtex":"@TechReport{Mueller17a,\n author = {Moritz M\\\"{u}ller and Giovane C. M. Moura and\n Ricardo de O. Schmidt and John Heidemann},\n title = \"Recursives in the Wild: Engineering Authoritative {DNS} Servers\",\n\tinstitution = \"USC/Information Sciences Institute\",\n\tyear = \t\t2017,\n\tsortdate = \t\t\"2017-06-02\", \n\tproject = \"ant, lacrend, retrofuturebridge\",\n\tjsubject = \"routing\",\n\tnumber =\t\"ISI-TR-720\",\n\tmonth =\t\tjun,\n\tjlocation =\t\"johnh: pafile\",\n\tkeywords =\t\"anycast, recursive DNS, authoritative selection\",\n\turl =\t\t\"https://ant.isi.edu/%7ejohnh/PAPERS/Mueller17a.html\",\n\tpdfurl =\t\"https://ant.isi.edu/%7ejohnh/PAPERS/Mueller17a.pdf\",\n\tmyorganization =\t\"USC/Information Sciences Institute\",\n\tcopyrightholder = \"authors\",\n\tabstract = \"In Internet Domain Name System (DNS), services \noperate \\emph{authoritative} name servers that individuals query \nthrough \\emph{recursive resolvers}. Operators strive to provide reliability\nby operating multiple name servers (NS), each on a separate IP\naddress, and by using IP anycast to allow NSes to provide service from\nmany physical locations. To meet their goals of minimizing latency\nand balancing load across NSes and anycast, operators need to know how\nrecursive resolvers select an NS, and how that interacts with their NS\ndeployments. Prior work has shown some recursives search for low\nlatency, while others pick an NS at random or round robin, but did not\nexamine how prevalent each choice was. This paper provides the first\nanalysis of how recursives select between name servers in the wild,\nand from that we provide guidance to name server operators to reach\ntheir goals. We conclude that all NSes need to be equally strong and\ntherefore we recommend to deploy IP anycast at every single\nauthoritative.\",\n}\n\n","author_short":["Müller, M.","Moura, G. C. M.","de O. Schmidt, R.","Heidemann, J."],"bibbaseid":"mller-moura-deoschmidt-heidemann-recursivesinthewildengineeringauthoritativednsservers-2017","role":"author","urls":{"Paper":"https://ant.isi.edu/%7ejohnh/PAPERS/Mueller17a.html"},"keyword":["anycast","recursive DNS","authoritative selection"],"metadata":{"authorlinks":{}}},"bibtype":"techreport","biburl":"https://bibbase.org/f/dHevizJoWEhWowz8q/johnh-2023-2.bib","dataSources":["YLyu3mj3xsBeoqiHK","fLZcDgNSoSuatv6aX","fxEParwu2ZfurScPY","7nuQvtHTqKrLmgu99"],"keywords":["anycast","recursive dns","authoritative selection"],"search_terms":["recursives","wild","engineering","authoritative","dns","servers","müller","moura","de o. schmidt","heidemann"],"title":"Recursives in the Wild: Engineering Authoritative DNS Servers","year":2017}