@TechReport{Fan12a,
	author = 	"Xun Fan and John Heidemann and Ramesh Govindan",
	title = 	"Characterizing Anycast in the Domain Name System",
	institution = 	"USC/Information Sciences Institute",
	year = 		2012,
	sortdate = 		"2012-05-01",
	project = "ant, amite, lacrend, lander, rearch_root, nipet",
	jsubject = "chronological",
	number = 	"ISI-TR-2011-681",
	month = 	may,
	jlocation = 	"johnh: pafile",
	keywords = 	"anycast, detection",
	jlocation = 	"johnh: pafile",
	keywords = 	"anycast, discovery, topology, DNS, F-root, PCH, Netalyzr",
	url =		"https://ant.isi.edu/%7ejohnh/PAPERS/Fan12a.html",
	pdfurl =	"https://ant.isi.edu/%7ejohnh/PAPERS/Fan12a.pdf",
	myorganization =	"USC/Information Sciences Institute",
	copyrightholder = "authors",
	abstract = "IP anycast is a central part of production DNS.  While prior work has
explored proximity, affinity and load balancing for some anycast
services, there has been little attention to third-party discovery and
enumeration of components of an anycast service.  Enumeration can
reveal abnormal service configurations, benign masquerading or hostile
hijacking of anycast services, and can help characterize the extent of
anycast deployment.  In this paper, we discuss two methods to identify
and characterize anycast nodes.  The first uses an existing anycast
diagnosis method based on CHAOS-class DNS records but augments it with
traceroute to resolve ambiguities.  The second proposes Internet-class
DNS records which permit accurate discovery through the use of
existing recursive DNS infrastructure.  We validate these two methods
against three widely-used anycast DNS services, using a very large
number (60k and 300k) of vantage points, and show that they can
provide excellent precision and recall.  Finally, we use these methods
to evaluate anycast deployments in top-level domains (TLDs), and find
one case where a third-party operates a server masquerading as a root
DNS anycast node as well as a noticeable proportion of unusual anycast
proxies.  We also show that, across all TLDs, up to 72\% use anycast,
and that, of about 30 anycast providers, the two largest serve nearly
half the anycasted TLD nameservers.
",
}

{"_id":"JqTnzskn58jnWz6o2","bibbaseid":"fan-heidemann-govindan-characterizinganycastinthedomainnamesystem-2012","author_short":["Fan, X.","Heidemann, J.","Govindan, R."],"bibdata":{"bibtype":"techreport","type":"techreport","author":[{"firstnames":["Xun"],"propositions":[],"lastnames":["Fan"],"suffixes":[]},{"firstnames":["John"],"propositions":[],"lastnames":["Heidemann"],"suffixes":[]},{"firstnames":["Ramesh"],"propositions":[],"lastnames":["Govindan"],"suffixes":[]}],"title":"Characterizing Anycast in the Domain Name System","institution":"USC/Information Sciences Institute","year":"2012","sortdate":"2012-05-01","project":"ant, amite, lacrend, lander, rearch_root, nipet","jsubject":"chronological","number":"ISI-TR-2011-681","month":"May","jlocation":"johnh: pafile","keywords":"anycast, discovery, topology, DNS, F-root, PCH, Netalyzr","url":"https://ant.isi.edu/%7ejohnh/PAPERS/Fan12a.html","pdfurl":"https://ant.isi.edu/%7ejohnh/PAPERS/Fan12a.pdf","myorganization":"USC/Information Sciences Institute","copyrightholder":"authors","abstract":"IP anycast is a central part of production DNS. While prior work has explored proximity, affinity and load balancing for some anycast services, there has been little attention to third-party discovery and enumeration of components of an anycast service. Enumeration can reveal abnormal service configurations, benign masquerading or hostile hijacking of anycast services, and can help characterize the extent of anycast deployment. In this paper, we discuss two methods to identify and characterize anycast nodes. The first uses an existing anycast diagnosis method based on CHAOS-class DNS records but augments it with traceroute to resolve ambiguities. The second proposes Internet-class DNS records which permit accurate discovery through the use of existing recursive DNS infrastructure. We validate these two methods against three widely-used anycast DNS services, using a very large number (60k and 300k) of vantage points, and show that they can provide excellent precision and recall. Finally, we use these methods to evaluate anycast deployments in top-level domains (TLDs), and find one case where a third-party operates a server masquerading as a root DNS anycast node as well as a noticeable proportion of unusual anycast proxies. We also show that, across all TLDs, up to 72% use anycast, and that, of about 30 anycast providers, the two largest serve nearly half the anycasted TLD nameservers. ","bibtex":"@TechReport{Fan12a,\n\tauthor = \t\"Xun Fan and John Heidemann and Ramesh Govindan\",\n\ttitle = \t\"Characterizing Anycast in the Domain Name System\",\n\tinstitution = \t\"USC/Information Sciences Institute\",\n\tyear = \t\t2012,\n\tsortdate = \t\t\"2012-05-01\",\n\tproject = \"ant, amite, lacrend, lander, rearch_root, nipet\",\n\tjsubject = \"chronological\",\n\tnumber = \t\"ISI-TR-2011-681\",\n\tmonth = \tmay,\n\tjlocation = \t\"johnh: pafile\",\n\tkeywords = \t\"anycast, detection\",\n\tjlocation = \t\"johnh: pafile\",\n\tkeywords = \t\"anycast, discovery, topology, DNS, F-root, PCH, Netalyzr\",\n\turl =\t\t\"https://ant.isi.edu/%7ejohnh/PAPERS/Fan12a.html\",\n\tpdfurl =\t\"https://ant.isi.edu/%7ejohnh/PAPERS/Fan12a.pdf\",\n\tmyorganization =\t\"USC/Information Sciences Institute\",\n\tcopyrightholder = \"authors\",\n\tabstract = \"IP anycast is a central part of production DNS. While prior work has\nexplored proximity, affinity and load balancing for some anycast\nservices, there has been little attention to third-party discovery and\nenumeration of components of an anycast service. Enumeration can\nreveal abnormal service configurations, benign masquerading or hostile\nhijacking of anycast services, and can help characterize the extent of\nanycast deployment. In this paper, we discuss two methods to identify\nand characterize anycast nodes. The first uses an existing anycast\ndiagnosis method based on CHAOS-class DNS records but augments it with\ntraceroute to resolve ambiguities. The second proposes Internet-class\nDNS records which permit accurate discovery through the use of\nexisting recursive DNS infrastructure. We validate these two methods\nagainst three widely-used anycast DNS services, using a very large\nnumber (60k and 300k) of vantage points, and show that they can\nprovide excellent precision and recall. Finally, we use these methods\nto evaluate anycast deployments in top-level domains (TLDs), and find\none case where a third-party operates a server masquerading as a root\nDNS anycast node as well as a noticeable proportion of unusual anycast\nproxies. We also show that, across all TLDs, up to 72\\% use anycast,\nand that, of about 30 anycast providers, the two largest serve nearly\nhalf the anycasted TLD nameservers.\n\",\n}\n\n","author_short":["Fan, X.","Heidemann, J.","Govindan, R."],"bibbaseid":"fan-heidemann-govindan-characterizinganycastinthedomainnamesystem-2012","role":"author","urls":{"Paper":"https://ant.isi.edu/%7ejohnh/PAPERS/Fan12a.html"},"keyword":["anycast","discovery","topology","DNS","F-root","PCH","Netalyzr"],"metadata":{"authorlinks":{}}},"bibtype":"techreport","biburl":"https://bibbase.org/f/dHevizJoWEhWowz8q/johnh-2023-2.bib","dataSources":["YLyu3mj3xsBeoqiHK","fLZcDgNSoSuatv6aX","fxEParwu2ZfurScPY","7nuQvtHTqKrLmgu99"],"keywords":["anycast","discovery","topology","dns","f-root","pch","netalyzr"],"search_terms":["characterizing","anycast","domain","name","system","fan","heidemann","govindan"],"title":"Characterizing Anycast in the Domain Name System","year":2012}