Insight into Anycast DNS Traffic Delivery Experiment
Explore findings from a field measurement experiment on Anycast DNS root traffic delivery, analyzing client queries, resolver behavior, and more. Discover how clients interact with anycast nodes and the impact on user experience based on resolver and node selection. Uncover insights into resolver and client behavior in hitting root servers and the effects of resolver routing on home proximity.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
Field measurement of Anycast DNS root traffic delivery Joao Damas Geoff Huston @apnic.net March 2018
Basic question Do clients ask the any cast nodes you think they do? Users experience depends on the local choice of resolver and on the resolver s choice of any cast node
Measure it Designed an experiment to see the details of how clients send queries that hit the root servers. Initial study with K-root data. Thank you RIPE NCC!
The experiment APNIC DNS APNIC DNS Root Root APNIC Web Server APNIC Web Server Learn about the Learn about the resolver resolver Learn about the Learn about the client client Learn about the Learn about the resolver and the resolver and the client search list client search list Resolver Resolver Client Client
Anycast routing for the prize QA:doh DE:ber US:rno MV PS LT ZA:jnb DE:fra CH:gva IN:bom BG:sof UY:mvd HU:bud LV:rix US:mia RU:led CH:zrh US:mkc RU:mow IR:thr US:ric KW:kwi JP:tyo RS:beg AT:vie RO:buh GR:ath FR:par IT:mil KZ:plx NL:ams PL:poz CZ:prg DE:ham AU:bne IS:rey PL:gdy GB:lon KE AT SI LK CA AR RS LT CO KG GB VN EE RU CA JO VN BA RS US CY MC SI UZ US SK SK LT PH FO DZ US Most resolvers are pretty good at hitting they closest any cast node ISPs usually have their routing act together
Resolver at the clients A lot more clients make sub-optimal geo choices for resolvers They end up far from home but it is not the resolver s fault Is it Google DNS? Nope. At least 76% of these go to OpenDNS addresses
TLDs, or something Trailing Domains added by clients 12000 10000 TLD home belkin lan local dlink asus cpe homestati on localdom ain fcname totolink % 67,2 % 4,4 % 4,1 % 2,6 % 1,8 % 1,7 % 1,1 % 8000 6000 1,0 % 1,0 % 1,0 % 1,0 % 4000 2000 0
