Visible to the public Anycast vs. DDoS: Evaluating the November 2015 Root DNS Event

TitleAnycast vs. DDoS: Evaluating the November 2015 Root DNS Event
Publication TypeConference Paper
Year of Publication2016
AuthorsMoura, Giovane C.M., Schmidt, Ricardo de O., Heidemann, John, de Vries, Wouter B., Muller, Moritz, Wei, Lan, Hesselman, Cristian
Conference NameProceedings of the 2016 Internet Measurement Conference
Conference LocationNew York, NY, USA
ISBN Number978-1-4503-4526-2
Keywordsanycast, BGP, Cyber Dependencies, DDoS, distributed denial-of-service, Human Behavior, IP, Performance, pubcrawl, reachability, resilience, root dns, Scalability
AbstractDistributed Denial-of-Service (DDoS) attacks continue to be a major threat on the Internet today. DDoS attacks overwhelm target services with requests or other traffic, causing requests from legitimate users to be shut out. A common defense against DDoS is to replicate a service in multiple physical locations/sites. If all sites announce a common prefix, BGP will associate users around the Internet with a nearby site, defining the catchment of that site. Anycast defends against DDoS both by increasing aggregate capacity across many sites, and allowing each site's catchment to contain attack traffic, leaving other sites unaffected. IP anycast is widely used by commercial CDNs and for essential infrastructure such as DNS, but there is little evaluation of anycast under stress. This paper provides the first evaluation of several IP anycast services under stress with public data. Our subject is the Internet's Root Domain Name Service, made up of 13 independently designed services ("letters", 11 with IP anycast) running at more than 500 sites. Many of these services were stressed by sustained traffic at 100× normal load on Nov. 30 and Dec. 1, 2015. We use public data for most of our analysis to examine how different services respond to stress, and identify two policies: sites may absorb attack traffic, containing the damage but reducing service to some users, or they may withdraw routes to shift both good and bad traffic to other sites. We study how these deployment policies resulted in different levels of service to different users during the events. We also show evidence of collateral damage on other services located near the attacks.
Citation Keymoura_anycast_2016