1. DNS and CDNs (Content Distribution Networks) Paul Francis Cornell Computer Science

2. What do all of these have in common? http://www.cnn.com/news/story.html HTTP (web) mailto://francis@cs.cornell.edu Email sip://service@phone.verizon.com SIP (Session Initiation Protocol)

3. They all have a DNS name somewhere http://www.cnn.com/news/story.html HTTP (web) francis@cs.cornell.edu Email sip://service@phone.verizon.com SIP (Session Initiation Protocol)

4. Why is DNS so important? Names are easier to remember than IP addresses paul@129.48.55.233 ???129.48.55.233 And in any event, IP addresses are not “dependable” They change often (dialup) They are not all unique

5. DNS is the “core” of the Internet So “we” (humans, and applications) like to deal with dependable, stable, friendly DNS names The names get “mapped” into IP addresses by lower layers By the Domain Name System (DNS) Then the learned IP address is put into packets, and IP routing gets the packets across the Internet

6. Picture of DNS query/reply

7. Why all these dots? Why falcon.cs.cornell.edu? Why not “cornell-falcon” or something?

8. It wasn’t always that way Twenty years ago, this was a valid email address: george@isi How did my computer learn the IP address of “isi”?

9. The “host table” and DNS Before DNS, there was the host table This was a complete list of all the hosts in the Internet! It was copied every night to every machine on the Internet! At some point, this was perceived as a potential scaling bottleneck… So a distributed directory called the “Domain Name System” was invented (DNS)

10. The host table (historic) Host NameIP Address mit-dlab133.65.14.77 isi-mail24.72.188.13 mit-lcs133.65.29.1 ……

11. Distributed Directory A primary goal of DNS was to have a distributed “host table”, so that each site could manage its own name-to- address mapping But also, it should scale well!

12. DNS is simple but powerful Only one type of query Query(domain name, RR type) Resource Record (RR) type is like an attribute type Answer(values, additional RRs) Limited number of RR types Hard to make new RR types Not for technical reasons… Rather because each requires global agreement

13. DNS is the core of the Internet Global name space Can be the core of a naming or identifying scheme Global directory service Can resolve a name to nearly every computer on the planet

14. Important DNS RR types NS: Points to next Name Server down the tree A: Contains the IP address AAAA for IPv6 MX: Contains the name of the mail server Service-oriented RR types SRV: Contains addresses and ports of services on servers One way to learn what port number to use NAPTR: Essentially a generalized mapping from one name space (i.e. phone numbers) to another (i.e. SIP URL)

15. DNS tree structure. edu. cornell.edu. cs.cornell.edu. com.jp.us. cmu.edu.mit.edu. eng.cornell.edu. foo.cs.cornell.eduA10.1.1.1 bar.cs.cornell.eduA10.1.1.1 NS RR “pointers”

16. Primary and secondary servers cornell.edu. cs.cornell.edu. NS RRs point to both primary and secondary servers RRs are initially configured into primary server Primary server replicates RRs onto secondary servers periodically (updates are incremental)

17. Resolver structure and configuration. edu. cornell.edu. cs.cornell.edu. com.jp. cmu.edu. eng.cornell.edu. Static configuration of root servers Stub resolver resides on client host, points to configured recursive server Resolver manages DNS queries on behalf of stub resolvers

18. Resolver structure and configuration. edu. cornell.edu. cs.cornell.edu. com.jp. cmu.edu. eng.cornell.edu. 1. Stub resolver sends recursive query 2,3,4… Resolver makes iterative queries to servers N. Resolver returns final answer to stub resolver (which also caches result) Resolver caches results for efficiency

19. DNS cache management All RRs have Time-to-live (TTL) values When TTL expires, cache entries are removed NS RRs tend to have long TTLs Cached for a long time Reduces load on higher level servers A RRs may have very short TTLs Order one minute for some web services Order one day for typical hosts

20. Caching is the key to performance Without caching, the small number of machines at the top of the hierarchy would be overwhelmed But what if you want to change the IP address of a host? How do you change all those cached entries around the world? You can’t…you wait until they timeout on their own, then make your change

21. Changing a DNS name Say your TTL was set to one day This means that even if you change DNS now, some hosts will continue to use the old address for a day So, give the host two IP addresses for a while (the old one and the new one) But DNS only answers with the new one After a day, the old one is cleaned out of caches, and you can remove it from the host

22. DNS Issues DoS attacks on (13) root servers DoS = Denial of Service Mis-configuration issues But on the whole DNS is an incredible system, and is in many important respects is the “core” of the Internet http://www.cnn.com/news francis@cs.cornell.edu

23. Next, Content Distribution Networks Idea here is to replicate a “web server” in many places over the Internet Latency to a single centralized web server farm may be too high A centralized web server farm may fail

24. Content Routing Principle (a.k.a. Content Distribution Network) S ISP Backbone ISP IX SS Site S ISP SSS SS Backbone ISP Backbone ISP Hosting Center Hosting Center Sites

25. Content Routing Principle (a.k.a. Content Distribution Network) S ISP Backbone ISP IX SS Site S ISP SSS SS Backbone ISP Backbone ISP Hosting Center Hosting Center Sites CS Content Origin here at Origin Server Content Servers distributed throughout the Internet OS

26. Content Routing Principle (a.k.a. Content Distribution Network) S ISP Backbone ISP IX SS Site S ISP SSS SS Backbone ISP Backbone ISP Hosting Center Hosting Center Sites CS Content is served from content servers nearer to the client CC OS

27. Two basic types of CDN: cached and pushed S ISP Backbone ISP IX SS Site S ISP SSS SS Backbone ISP Backbone ISP Hosting Center Hosting Center Sites CS CC OS

28. Cached CDN S ISP Backbone ISP IX SS Site S ISP SSS SS Backbone ISP Backbone ISP Hosting Center Hosting Center Sites CS 1.Client requests content. CC OS

29. Cached CDN S ISP Backbone ISP IX SS Site S ISP SSS SS Backbone ISP Backbone ISP Hosting Center Hosting Center Sites CS 1.Client requests content. 2.CS checks cache, if miss gets content from origin server. CC OS

30. Cached CDN S ISP Backbone ISP IX SS Site S ISP SSS SS Backbone ISP Backbone ISP Hosting Center Hosting Center Sites CS 1.Client requests content. 2.CS checks cache, if miss gets content from origin server. 3.CS caches content, delivers to client. CC OS

31. Cached CDN S ISP Backbone ISP IX SS Site S ISP SSS SS Backbone ISP Backbone ISP Hosting Center Hosting Center Sites CS 1.Client requests content. 2.CS checks cache, if miss gets content from origin server. 3.CS caches content, delivers to client. 4.Delivers content out of cache on subsequent requests. CC OS

32. Pushed CDN S ISP Backbone ISP IX SS Site S ISP SSS SS Backbone ISP Backbone ISP Hosting Center Hosting Center Sites CS 1.Origin Server pushes content out to all CSs. C OS C

33. Pushed CDN S ISP Backbone ISP IX SS Site S ISP SSS SS Backbone ISP Backbone ISP Hosting Center Hosting Center Sites CS 1.Origin Server pushes content out to all CSs. 2.Request served from CSs. C C OS

34. CDN benefits Content served closer to client Less latency, better performance Load spread over multiple distributed CSs More robust (to ISP failure as well as other failures) Handle flashes better (load spread over ISPs) But well-connected, replicated Hosting Centers can do this too

35. CDN costs and limitations Cached CDNs can’t deal with dynamic/personalized content More and more content is dynamic “Classic” CDNs limited to images Managing content distribution is non-trivial Tension between content lifetimes and cache performance Dynamic cache invalidation Keeping pushed content synchronized and current

36. What if lots of clients try to access the same CS? S ISP Backbone ISP IX SS Site S ISP SSS SS Backbone ISP Backbone ISP Hosting Center Hosting Center Sites CS C C OS CCC C

37. How can the CDN spread this load around? S ISP Backbone ISP IX SS Site S ISP SSS SS Backbone ISP Backbone ISP Hosting Center Hosting Center Sites CS C C OS CCC C

38. Guess what: DNS! Smart DNS server monitors load on the content servers When it answers a DNS request, it picks a server that is not overloaded (and near the client) The DNS answer has a small TTL (30 seconds – one minute) Small TTL allows the DNS load balancer to make fine-grained load decisions Can quickly offload a busy or even crashed content server

39. How well do CDNs work? Hard to say… Some evidence suggests they are not so good a picking nearby servers Internet bandwidth is improving, so not as important to pick nearby servers Central hosting centers are easier to manage, and perform increasingly well In fact, Akamai is beginning to find it difficult to justify its service!