1 / 16

Chapter 2 Application Layer

Chapter 2 Application Layer. 2.5 DNS. Computer Networking: A Top Down Approach 6 th edition Jim Kurose, Keith Ross Addison-Wesley March 2012. Chapter 2: outline. 2.1 principles of network applications app architectures app requirements 2.2 Web and HTTP 2.3 FTP 2.4 electronic mail

wendi
Download Presentation

Chapter 2 Application Layer

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Chapter 2Application Layer 2.5 DNS Computer Networking: A Top Down Approach 6th edition Jim Kurose, Keith RossAddison-WesleyMarch 2012 Application Layer

  2. Chapter 2: outline 2.1 principles of network applications app architectures app requirements 2.2 Web and HTTP 2.3 FTP 2.4 electronic mail SMTP, POP3, IMAP 2.5 DNS 2.6 P2P applications 2.7 socket programming with UDP and TCP Application Layer

  3. people: many identifiers: SSN, name, passport # Internet hosts, routers: IP address (32 bit) - used for addressing datagrams “name”, e.g., www.yahoo.com - used by humans Q: how to map between IP address and name, and vice versa ? Domain Name System: distributed database implemented in hierarchy of many name servers application-layer protocol: hosts, name servers communicate to resolvenames (address/name translation) note: core Internet function, implemented as application-layer protocol complexity at network’s “edge” DNS: domain name system Application Layer

  4. why not centralize DNS? single point of failure traffic volume distant centralized database maintenance DNS services hostname to IP address translation host aliasing canonical, alias names mail server aliasing load distribution replicated Web servers: many IP addresses correspond to one name DNS: services, structure A: doesn’t scale! Application Layer

  5. Root DNS Servers org DNS servers edu DNS servers com DNS servers poly.edu DNS servers umass.edu DNS servers yahoo.com DNS servers pbs.org DNS servers amazon.com DNS servers DNS: a distributed, hierarchical database … … top-level domain (TLD) DNS Servers authoritative DNS servers client wants IP for www.amazon.com; 1st approx: • client queries root server to find com DNS server • client queries .com DNS server to get amazon.com DNS server • client queries amazon.com DNS server to get IP address for www.amazon.com Application Layer

  6. contacted by local name server that can not resolve name root name server: contacts authoritative name server if name mapping not known gets mapping returns mapping to local name server DNS: root name servers c. Cogent, Herndon, VA (5 other sites) d. U Maryland College Park, MD h. ARL Aberdeen, MD j. Verisign, Dulles VA (69 other sites ) k. RIPE London (17 other sites) i. Netnod, Stockholm (37 other sites) m. WIDE Tokyo (5 other sites) e. NASA Mt View, CA f. Internet Software C. Palo Alto, CA (and 48 other sites) 13 root name “servers” worldwide a. Verisign, Los Angeles CA (5 other sites) b. USC-ISI Marina del Rey, CA l. ICANN Los Angeles, CA (41 other sites) g. US DoD Columbus, OH (5 other sites) Application Layer

  7. TLD, authoritative servers top-level domain (TLD) servers: • responsible for com, org, net, edu, aero, jobs, museums, and all top-level country domains, e.g.: uk, fr, ca, jp • Network Solutions maintains servers for .com TLD • Educause for .edu TLD authoritative DNS servers: • organization’s own DNS server(s), providing authoritative hostname to IP mappings for organization’s named hosts • can be maintained by organization or service provider Application Layer

  8. Local DNS name server • does not strictly belong to hierarchy • each ISP (residential ISP, company, university) has one • also called “default name server” • when host makes DNS query, query is sent to its local DNS server • has local cache of recent name-to-address translation pairs (but may be out of date!) • acts as proxy, forwards query into hierarchy Application Layer

  9. host at cis.poly.edu wants IP address for gaia.cs.umass.edu local DNS server dns.poly.edu DNS name resolution example root DNS server 2 3 TLD DNS server 4 5 iterated query: • contacted server replies with name of server to contact • “I don’t know this name, but ask this server” 6 7 1 8 authoritative DNS server dns.cs.umass.edu requesting host cis.poly.edu gaia.cs.umass.edu Application Layer

  10. local DNS server dns.poly.edu DNS name resolution example root DNS server 3 2 7 recursive query: • puts burden of name resolution on contacted name server • heavy load at upper levels of hierarchy? 6 TLD DNS server 4 5 1 8 authoritative DNS server dns.cs.umass.edu requesting host cis.poly.edu gaia.cs.umass.edu Application Layer

  11. once (any) name server learns mapping, it caches mapping cache entries timeout (disappear) after some time (TTL) TLD servers typically cached in local name servers thus root name servers not often visited cached entries may be out-of-date (best effort name-to-address translation!) if name host changes IP address, may not be known Internet-wide until all TTLs expire update/notify mechanisms proposed IETF standard RFC 2136 DNS: caching, updating records Application Layer

  12. DNS: distributed db storing resource records (RR) type=NS name is domain (e.g., foo.com) value is hostname of authoritative name server for this domain DNS records RR format:(name, value, type, ttl) type=A • nameis hostname • valueis IP address type=CNAME • name is alias name for some “canonical” (the real) name • www.ibm.comis really servereast.backup2.ibm.com • valueis canonical name (relay1.bar.foo.com, 145.37.93.126, A) (foo.com, relay1.bar.foo.com, CNAME) type=MX • valueis name of mailserver associated withname (foo.com, dns.foo.com, NS) (foo.com, mail.bar.foo.com, MX) Application Layer

  13. queryand reply messages, both with same message format 2 bytes 2 bytes identification flags # questions # answer RRs # additional RRs # authority RRs questions (variable # of questions) answers (variable # of RRs) authority (variable # of RRs) additional info (variable # of RRs) DNS protocol, messages msg header • identification: 16 bit # for query, reply to query uses same # • flags: • query or reply • recursion desired • recursion available • reply is authoritative Application Layer

  14. 2 bytes 2 bytes identification flags # questions # answer RRs # additional RRs # authority RRs questions (variable # of questions) answers (variable # of RRs) authority (variable # of RRs) additional info (variable # of RRs) DNS protocol, messages name, type fields for a query RRs in response to query records for authoritative servers additional “helpful” info that may be used Application Layer

  15. Inserting records into DNS • example: new startup “Network Utopia” • register name networkuptopia.com at DNS registrar (e.g., Network Solutions) • provide names, IP addresses of authoritative name server (primary and secondary) • registrar inserts two RRs into .com TLD server:(networkutopia.com, dns1.networkutopia.com, NS) (dns1.networkutopia.com, 212.212.212.1, A) • create authoritative server type A record for www.networkuptopia.com; type MX record for networkutopia.com Application Layer

  16. Attacking DNS DDoS attacks • Bombard root servers with traffic • Not successful to date • Traffic Filtering • Local DNS servers cache IPs of TLD servers, allowing root server bypass • Bombard TLD servers • Potentially more dangerous Redirect attacks • Man-in-middle • Intercept queries • DNS poisoning • Send bogus relies to DNS server, which caches Exploit DNS for DDoS • Send queries with spoofed source address: target IP • Requires amplification Application Layer

More Related