diversity in dns performance measures
play

Diversity in DNS Performance Measures Richard Liston, Sridhar - PowerPoint PPT Presentation

Diversity in DNS Performance Measures Richard Liston, Sridhar Srinivasan and Ellen Zegura liston,sridhar,ewz@cc.gatech.edu Georgia Institute of Technology Diversity in DNSPerformance Measures p.1/22 Roadmap Background: DNS Problem:


  1. Diversity in DNS Performance Measures Richard Liston, Sridhar Srinivasan and Ellen Zegura liston,sridhar,ewz@cc.gatech.edu Georgia Institute of Technology Diversity in DNSPerformance Measures – p.1/22

  2. Roadmap Background: DNS Problem: Measuring DNS Our method: requirements and solution Results Conclusions Diversity in DNSPerformance Measures – p.2/22

  3. DNS: Domain Name System Solution to the problem of global addressing Distributed database over hierarchical namespace Allows for local administration of Namespace (via delegation of authority over zones) Caching policies (via TTL) Details hidden from users ( gethostbyname() ) Supported by: root servers: .gov, .edu, .fr, ... gTLD servers: .com, .org, ... other servers: lower levels in the namespace hierarchy Diversity in DNSPerformance Measures – p.3/22

  4. What Happens in the Wild... A.ROOT-SERVERS.NET B.ROOT-SERVERS.NET M.ROOT-SERVERS.NET A.GTLD-SERVERS.NET B.GTLD-SERVERS.NET M.GTLD-SERVERS.NET gatech.edu itchy.mindspring.net LOCAL DNS SERVER zeon.cc.gatech.edu CLIENT gaia.cc.gatech.edu cnn.com Diversity in DNSPerformance Measures – p.4/22

  5. What Happens in the Wild... A.ROOT-SERVERS.NET B.ROOT-SERVERS.NET M.ROOT-SERVERS.NET A.GTLD-SERVERS.NET B.GTLD-SERVERS.NET M.GTLD-SERVERS.NET gatech.edu itchy.mindspring.net LOCAL DNS SERVER zeon.cc.gatech.edu CLIENT gaia.cc.gatech.edu cnn.com Diversity in DNSPerformance Measures – p.4/22

  6. What Happens in the Wild... A.ROOT-SERVERS.NET B.ROOT-SERVERS.NET M.ROOT-SERVERS.NET A.GTLD-SERVERS.NET B.GTLD-SERVERS.NET M.GTLD-SERVERS.NET gatech.edu itchy.mindspring.net LOCAL DNS SERVER zeon.cc.gatech.edu CLIENT gaia.cc.gatech.edu cnn.com Diversity in DNSPerformance Measures – p.4/22

  7. What Happens in the Wild... A.ROOT-SERVERS.NET B.ROOT-SERVERS.NET M.ROOT-SERVERS.NET A.GTLD-SERVERS.NET B.GTLD-SERVERS.NET M.GTLD-SERVERS.NET gatech.edu itchy.mindspring.net LOCAL DNS SERVER zeon.cc.gatech.edu CLIENT gaia.cc.gatech.edu cnn.com Diversity in DNSPerformance Measures – p.4/22

  8. What Happens in the Wild... A.ROOT-SERVERS.NET B.ROOT-SERVERS.NET M.ROOT-SERVERS.NET A.GTLD-SERVERS.NET B.GTLD-SERVERS.NET M.GTLD-SERVERS.NET gatech.edu itchy.mindspring.net LOCAL DNS SERVER zeon.cc.gatech.edu CLIENT gaia.cc.gatech.edu cnn.com Diversity in DNSPerformance Measures – p.4/22

  9. What Happens in the Wild... A.ROOT-SERVERS.NET B.ROOT-SERVERS.NET M.ROOT-SERVERS.NET A.GTLD-SERVERS.NET B.GTLD-SERVERS.NET M.GTLD-SERVERS.NET gatech.edu itchy.mindspring.net LOCAL DNS SERVER zeon.cc.gatech.edu CLIENT gaia.cc.gatech.edu cnn.com Diversity in DNSPerformance Measures – p.4/22

  10. What Happens in the Wild... A.ROOT-SERVERS.NET B.ROOT-SERVERS.NET M.ROOT-SERVERS.NET A.GTLD-SERVERS.NET B.GTLD-SERVERS.NET M.GTLD-SERVERS.NET gatech.edu itchy.mindspring.net LOCAL DNS SERVER zeon.cc.gatech.edu CLIENT gaia.cc.gatech.edu cnn.com Diversity in DNSPerformance Measures – p.4/22

  11. What Happens in the Wild... A.ROOT-SERVERS.NET B.ROOT-SERVERS.NET M.ROOT-SERVERS.NET A.GTLD-SERVERS.NET B.GTLD-SERVERS.NET M.GTLD-SERVERS.NET gatech.edu itchy.mindspring.net LOCAL DNS SERVER zeon.cc.gatech.edu CLIENT gaia.cc.gatech.edu cnn.com Diversity in DNSPerformance Measures – p.4/22

  12. What Happens in the Wild... A.ROOT-SERVERS.NET B.ROOT-SERVERS.NET M.ROOT-SERVERS.NET A.GTLD-SERVERS.NET B.GTLD-SERVERS.NET M.GTLD-SERVERS.NET gatech.edu itchy.mindspring.net LOCAL DNS SERVER zeon.cc.gatech.edu CLIENT gaia.cc.gatech.edu cnn.com Diversity in DNSPerformance Measures – p.4/22

  13. What Happens in the Wild... A.ROOT-SERVERS.NET B.ROOT-SERVERS.NET M.ROOT-SERVERS.NET A.GTLD-SERVERS.NET B.GTLD-SERVERS.NET M.GTLD-SERVERS.NET gatech.edu itchy.mindspring.net LOCAL DNS SERVER zeon.cc.gatech.edu CLIENT gaia.cc.gatech.edu cnn.com Diversity in DNSPerformance Measures – p.4/22

  14. What Happens in the Wild... A.ROOT-SERVERS.NET B.ROOT-SERVERS.NET M.ROOT-SERVERS.NET A.GTLD-SERVERS.NET B.GTLD-SERVERS.NET M.GTLD-SERVERS.NET gatech.edu itchy.mindspring.net LOCAL DNS SERVER zeon.cc.gatech.edu CLIENT gaia.cc.gatech.edu cnn.com Diversity in DNSPerformance Measures – p.4/22

  15. What Happens in the Wild... A.ROOT-SERVERS.NET B.ROOT-SERVERS.NET M.ROOT-SERVERS.NET A.GTLD-SERVERS.NET B.GTLD-SERVERS.NET M.GTLD-SERVERS.NET gatech.edu itchy.mindspring.net LOCAL DNS SERVER zeon.cc.gatech.edu CLIENT gaia.cc.gatech.edu cnn.com Diversity in DNSPerformance Measures – p.4/22

  16. Resolution Tree: Critical Path Query from client Query to gTLD Referral from gTLD Query to NS1 Query to NS2 Response from NS2 Timeout/re-xmit to NS1 Response to client Response from NS1 Diversity in DNSPerformance Measures – p.5/22

  17. Resolution Tree: Critical Path Query from client Query to gTLD Referral from gTLD Query to NS1 Query to NS2 Response from NS2 Timeout/re-xmit to NS1 Response to client Response from NS1 Diversity in DNSPerformance Measures – p.5/22

  18. A B C ... M Root Servers: A B C ... M GTLD Servers: Domain Servers: example.org example.com example.net 3 1 2 2 1 Client 1 Client 2 Diversity in DNSPerformance Measures – p.6/22

  19. Diversity in DNSPerformance Measures – p.7/22

  20. Measuring DNS Primary question in this study: To what extent do DNS performance measures for non-cached names vary across Internet locations? Measures: Overall response time Root and gTLD server response time Aliasing via CNAME TTL (Time-To-Live in seconds) Diversity in DNSPerformance Measures – p.8/22

  21. Measurement Method Criteria: Capture fine-grained information about DNS system operation Compare data collected at different sites Easily collect data at multiple locations Diversity in DNSPerformance Measures – p.9/22

  22. Measurement Method Criteria: Capture fine-grained information about DNS system operation Compare data collected at different sites Easily collect data at multiple locations Solution: Modify BIND to log relevant info: tx/rx packets, packet type, timeouts, timestamp Package modified BIND w/non-root config files and driving script w/15K domain names Use dig to query the modified server Domain names are diverse, non-cached Post-process logs Diversity in DNSPerformance Measures – p.9/22

  23. Data Collection NIMI nodes, colleagues and Linux users; 75 sites in 21 countries and territories (still need China and India!) Different days of week and times of day Variety of connection technologies: DSL, PPP, cable modem, GigE, etc. January 2002 and late March/early April 2002 Single run: 4 to 6 hours Very lightweight Diversity in DNSPerformance Measures – p.10/22

  24. Validating Workload Set Completion and success rates Response codes: 0: No error 2: Remote server failure 3: Name does not exist Completed (0 or 3): 96.4% to 98.1% Successful (0): 92.7% to 94.7% Diversity in DNSPerformance Measures – p.11/22

  25. Mean Response Time, com- pleted (MRTc) Mean response time of completed lookups (sec) 2.2 2.0 1.8 1.6 1.4 1.2 1.0 0 20 40 60 Sites Range from 0.95 seconds to 2.31 seconds! Diversity in DNSPerformance Measures – p.12/22

  26. Measuring Major Factors Connectivity MINc: Minimum response time for completed lookups Minimum round trip time to closest name server queried Diversity in DNSPerformance Measures – p.13/22

  27. Measuring Major Factors Connectivity MINc: Minimum response time for completed lookups Minimum round trip time to closest name server queried Loss Rate Total retries along all critical paths Diversity in DNSPerformance Measures – p.13/22

  28. Measuring Major Factors Connectivity MINc: Minimum response time for completed lookups Minimum round trip time to closest name server queried Loss Rate Total retries along all critical paths Root/GTLD server performance MRTr/MRTg: mean response time to root/gTLD servers Diversity in DNSPerformance Measures – p.13/22

  29. Measuring Major Factors Connectivity MINc: Minimum response time for completed lookups Minimum round trip time to closest name server queried Loss Rate Total retries along all critical paths Root/GTLD server performance MRTr/MRTg: mean response time to root/gTLD servers Location relative to other nameservers MRTl: mean response time to a fixed set of last nameservers contacted Diversity in DNSPerformance Measures – p.13/22

  30. Correlations Factor Correlation w/MRTc Connectivity (MINc) 0.62 Loss Rate (# retries) 0.50 Root Server Performance (MRTr) 0.86 GTLD Server Performance (MRTg) 0.94 Location (MRTl) 0.90 Diversity in DNSPerformance Measures – p.14/22

  31. Impact of Root/GTLD/Other 100 other gtld root 80 Percentage of access time 60 40 20 0 Sites Diversity in DNSPerformance Measures – p.15/22

  32. Some Implications Roots: poor performance barely noticable GTLDs: poor performance more noticable ( 20% - 30% of time spent in querying gTLD servers); better server placement could help Other servers: most potential for performance enhancement; do CDNs want to provide DNS-only services??? A service differentiator for ISPs may involve performance from gTLD servers ISPs may consider choosing different routes to gTLD servers Diversity in DNSPerformance Measures – p.16/22

Recommend


More recommend