EE 122: Domain Name Server (DNS)Names & AddressesInternet Centric ViewName ServiceGeneral ViewMappingName HierarchySlide 8Top Level DomainsDNS Name ServersServer Hierarchy: ZonesServer HierarchySlide 13Slide 14DNS: Root Name ServersSimple DNS ExampleDNS ExampleDNS: Iterated QueriesDiscussionSummaryEE 122: Domain Name Server (DNS)Ion StoicaNov 25, 2002(* based in part on on-line slides by J. Kurose & K. Rose and Raj Jain)[email protected] 2Names & AddressesWhat is a name?What is an address?What is the difference between names and [email protected] 3Internet Centric ViewAddresses: -Says how to reach an object it has location semantics associated to it-It’s in a format easy to process by computers Name: -Does not have any location semantics associated to it-It’s in a format easier to understand/read/remember by peopleExamples:-IP address: 169.229.131.109-Name: [email protected] 4Name ServiceName space: define the set of possible names-Hierarchical (e.g., Unix and Windows file names)-Flat Bindings: the mapping between names and values (e.g., addresses) -Bindings can be implemented by using tablesResolution: procedure that, when invoked with a name, returns the corresponding valueName server: specific implementation of a resolution mechanism that is available on the network and that can be queried by sending [email protected] 5General ViewIn general there are multiple mappingsHost name: arachne.berkeley.edu IP address: 169.229.131.109 Ethernet MAC address: 12.34.56.78.90.12 DNS resolutionARP (Address Resolution Protocol)[email protected] 6MappingMultiple names can map onto the same address-Example: www.berkeley.edu and arachne.berkeley.edu maps to the same machine (i.e., the same IP address)One name can map onto multiple addresses-Example: www.yahoo.com can be mapped to multiple [email protected] 7Name Hierarchyrooteducomgov milorgnet uk [email protected] 8Name HierarchyUnique domain suffix is assigned by the Internet AuthorityThe domain administrators have complete control over the domainNo limit on the number of subdomains or number of levelsName space is not related with the physical interconnection Geographical hierarchy is allowed (e.g., cnri.reston.va.us)A name could be a domain or an individual [email protected] 9Top Level DomainsDomain Name Assignmentcom Commercialedu Educational gov Government mil Military net Network org Other organizationscountry code au, uk, ca, …[email protected] 10DNS Name ServersWhy not centralize DNS? -Single point of failure-Traffic volume-Distant centralized database-MaintenanceDoesn’t [email protected] 11Server Hierarchy: ZonesA zone corresponds to an administrative authority that is responsible for that portion of the hierarchyrooteducomgov milorgnet uk [email protected] 12Server HierarchyServer are organized in hierarchiesEach server has authority over a portion of the hierarchy-A single node in the name hierarchy cannot be split-A server maintains only a subset of all names-It needs to know other servers that are responsible for the other portions of the [email protected] 13Server HierarchyAuthority: each server has the name to address translation table for all names in the name space it controlsEvery server knows the rootRoot server knows about all top-level [email protected] 14DNS Name ServersNo server has all name-to-IP address mappingsLocal name servers:-Each ISP (company) has local (default) name server-Host DNS query first go to local name serverAuthoritative name servers:-For a host: stores that host’s (name, IP address)-Can perform name/address translation for that host’s [email protected] 15DNS: Root Name ServersContacted by local name server that can not resolve nameRoot name server:-Contacts authoritative name server if name mapping not known-Gets mapping-Returns mapping to local name server~ Dozen root name servers [email protected] 16Simple DNS ExampleHost whsitler.cs.cmu.edu wants IP address of www.berkeley.edu1. Contacts its local DNS server, mango.srv.cs.cmu.edu2. mango.srv.cs.cmu.edu contacts root name server, if necessary3. Root name server contacts authoritative name server, ns1.berkeley.edu, if necessary requesting hostwhistler.cs.cmu.eduwww.berkeley.eduroot name serverauthorititive name serverns1.berkeley.edulocal name [email protected] 17DNS ExampleRoot name server:May not know authoritative name serverMay know intermediate name server: who to contact to find authoritative name server?requesting hostwhistler.cs.cmu.eduwww.berkeley.eduroot name serverlocal name servermango.srv.cs.cmu.edu123456authoritative name serverns1.berkeley.eduintermediate name server(edu server)[email protected] 18DNS: Iterated QueriesRecursive query:Puts burden of name resolution on contacted name serverHeavy load?Iterated query:Contacted server replies with name of server to contact“I don’t know this name, but ask this server”requesting hostwhistler.cs.cmu.eduwww.berkeley.eduroot name serverlocal name servermango.srv.cs.cmu.edu123467authoritative name serverns1.berkeley.eduintermediate name server(edu server)58iterated [email protected] 19DiscussionRobustness-Use multiple replicas, but…-…what if someone mounts a denial of service attack to all root servers?Performance:-Use caching to speed-up subsequent queries to the same nameWhat about update/notify?-Mechanisms under design by IETF (RFC 2136; http://www.ietf.org/html.charters/dnsind-charter.html)[email protected] 20SummaryDNS: maps names onto IP addressName space and the administration are both hierarchicalReplication: used to increase robustnessCaching: used to increase the
View Full Document