DOC PREVIEW
Berkeley ELENG 122 - Domain Name System

This preview shows page 1-2-17-18-19-35-36 out of 36 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 36 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 36 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 36 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 36 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 36 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 36 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 36 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 36 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

Slide 1Goals of Today’s LectureHost Names vs. IP addressesSeparating Naming and AddressingScalable (Name  Address) MappingsDomain Name System (DNS)Distributed Hierarchical DatabaseDNS RootDNS Root ServersDNS Root ServersTLD and Authoritative DNS ServersUsing DNSExampleHow did it know the root server IP?Recursive vs. Iterative QueriesReverse Mapping (Address  Host)Distributed Hierarchical DatabaseDNS CachingNegative CachingDNS Resource RecordsDNS ProtocolInteractive DNS lookups using digSlide 23Slide 24Slide 25Slide 26ReliabilityInserting Resource Records into DNSSetting up foobar.com, con’tSecurity Analysis of DNSSecurity Problem #1: StarbucksSecurity Problem #2: Cache PoisoningCache Poisoning, con’tCache Poisoning, con’tSummaryNext Lecture1EE 122: Domain Name SystemIon StoicaTAs: Junda Liu, DK Moon, David Zatshttp://inst.eecs.berkeley.edu/~ee122/(Materials with thanks to Vern Paxson, Jennifer Rexford,and colleagues at UC Berkeley)2Goals of Today’s LectureConcepts & principles underlying the Domain Name System (DNS)Indirection: names in place of addressesHierarchy: in names, addresses, and serversCaching: of mappings from names to/from addressesInner workings of DNSDNS resolvers and serversIterative and recursive queriesTTL-based cachingUse of the dig utilitySecurity analysis3Host Names vs. IP addressesHost namesMnemonic name appreciated by humansVariable length, full alphabet of charactersProvide little (if any) information about locationExamples: www.cnn.com and bbc.co.ukIP addressesNumerical address appreciated by routersFixed length, binary numberHierarchical, related to host locationExamples: 64.236.16.20 and 212.58.224.1314Separating Naming and AddressingNames are easier to rememberwww.cnn.com vs. 64.236.16.20Addresses can change underneathMove www.cnn.com to 4.125.91.21E.g., renumbering when changing providersName could map to multiple IP addresseswww.cnn.com to multiple (8) replicas of the Web siteEnablesLoad-balancingReducing latency by picking nearby serversTailoring content based on requester’s location/identityMultiple names for the same addressE.g., aliases like www.cnn.com and cnn.com5Scalable (Name  Address) MappingsOriginally: per-host fileFlat namespace/etc/hosts (what is this on your computer today?)SRI (Menlo Park) kept master copyDownloaded regularlySingle server doesn’t scaleTraffic implosion (lookups & updates)Single point of failureAmazing politicsNeed a distributed, hierarchical collection of servers6Domain Name System (DNS)Properties of DNSHierarchical name space divided into zonesZones distributed over collection of DNS serversHierarchy of DNS serversRoot (hardwired into other servers)Top-level domain (TLD) serversAuthoritative DNS serversPerforming the translationsLocal DNS serversResolver software7Distributed Hierarchical Databasecom edu org acukzwarpaunnamed rootbarwest eastfoo myaccamusrin-addrgeneric domains country domainsmy.east.bar.eduusr.cam.ac.ukTop-Level Domains (TLDs)8DNS RootLocated in Virginia, USAHow do we make the root scale? Verisign, Dulles, VA9DNS Root Servers13 root servers (see http://www.root-servers.org/)Labeled A through MDoes this scale?B USC-ISI Marina del Rey, CAL ICANN Los Angeles, CAE NASA Mt View, CAF Internet Software Consortium Palo Alto, CAI Autonomica, StockholmK RIPE LondonM WIDE TokyoA Verisign, Dulles, VAC Cogent, Herndon, VAD U Maryland College Park, MDG US DoD Vienna, VAH ARL Aberdeen, MDJ Verisign10DNS Root Servers13 root servers (see http://www.root-servers.org/)Labeled A through MReplication via any-casting (localized routing for addresses)B USC-ISI Marina del Rey, CAL ICANN Los Angeles, CAE NASA Mt View, CAF Internet Software Consortium, Palo Alto, CA (and 37 other locations)I Autonomica, Stockholm (plus 29 other locations)K RIPE London (plus 16 other locations)M WIDE Tokyo plus Seoul, Paris, San FranciscoA Verisign, Dulles, VAC Cogent, Herndon, VA (also Los Angeles, NY, Chicago)D U Maryland College Park, MDG US DoD Vienna, VAH ARL Aberdeen, MDJ Verisign (21 locations)11TLD and Authoritative DNS ServersTop-level domain (TLD) serversGeneric domains (e.g., com, org, edu)Country domains (e.g., uk, fr, cn, jp)Special domains (e.g., arpa)Typically managed professionallyNetwork Solutions maintains servers for “com”Educause maintains servers for “edu”Authoritative DNS serversProvide public records for hosts at an organizationPrivate records may differ, though not part of original design’s intentFor the organization’s servers (e.g., Web and mail)Can be maintained locally or by a service provider12Using DNSLocal DNS server (“default name server”)Usually near the endhosts that use itLocal hosts configured with local server (e.g., /etc/resolv.conf) or learn server via DHCPClient applicationExtract server name (e.g., from the URL)Do gethostbyname() to trigger resolver codeServer applicationExtract client IP address from socketOptional gethostbyaddr() to translate into name13requesting hostcis.poly.edugaia.cs.umass.eduroot DNS serverlocal DNS serverdns.poly.edu123456authoritative DNS serverdns.cs.umass.edu78TLD DNS serverExampleHost at cis.poly.edu wants IP address for gaia.cs.umass.edu14How did it know the root server IP?Hard-codedWhat if it changes?15Recursive vs. Iterative QueriesRecursive queryAsk server to get answer for youE.g., request 1 and response 8Iterative queryAsk server who to ask nextE.g., all other request-response pairsrequesting hostcis.poly.eduroot DNS serverlocal DNS serverdns.poly.edu123456authoritative DNS serverdns.cs.umass.edu78TLD DNS server16Reverse Mapping (Address  Host)How do we go the other direction, from an IP address to the corresponding hostname?Addresses already have natural “quad” hierarchy:12.34.56.78But: quad notation has most-sig. hierarchy element on left, while www.cnn.com has it on the rightIdea: reverse the quads = 78.56.34.12 …… and look that up in the DNSUnder what TLD?Convention: in-addr.arpaSo lookup is for 78.56.34.12.in-addr.arpa17Distributed Hierarchical Databasecom edu org acukzwarpaunnamed rootbarwest eastfoo myaccamusrin-addrgeneric domains country domainsmy.east.bar.eduusr.cam.ac.uk12345612.34.56.0/2418DNS CachingPerforming


View Full Document

Berkeley ELENG 122 - Domain Name System

Documents in this Course
Lecture 6

Lecture 6

22 pages

Wireless

Wireless

16 pages

Links

Links

21 pages

Ethernet

Ethernet

10 pages

routing

routing

11 pages

Links

Links

7 pages

Switches

Switches

30 pages

Multicast

Multicast

36 pages

Switches

Switches

18 pages

Security

Security

16 pages

Switches

Switches

18 pages

Lecture 1

Lecture 1

56 pages

OPNET

OPNET

5 pages

Lecture 4

Lecture 4

16 pages

Ethernet

Ethernet

65 pages

Models

Models

30 pages

TCP

TCP

16 pages

Wireless

Wireless

48 pages

Load more
Download Domain Name System
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Domain Name System and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Domain Name System 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?