DOC PREVIEW
Berkeley ELENG 122 - Domain Name Server - DNS

This preview shows page 1-2-23-24 out of 24 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 24 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 24 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 24 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 24 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 24 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

EE 122: Lecture 20 (Domain Name Server - DNS)Names & AddressesInternet Centric ViewGeneral ViewName ServiceSlide 6MappingName HierarchySlide 9Top Level DomainsDNS Name ServersServer Hierarchy: ZonesServer HierarchySlide 14Slide 15DNS: Root Name ServersSimple DNS ExampleDNS ExampleDNS: Iterated QueriesDNS RecordsDNS protocol, messagesSlide 22DiscussionSummaryEE 122: Lecture 20(Domain Name Server - DNS)Ion StoicaNov 15, 2001(* based on the some on-line slides of J. Kurose & K. Rose and of Raj Jain)[email protected] 2Names & AddressesWhat is a name?What is an address?What is an identifier?What is the difference between name, addresses, and [email protected] 3Internet Centric ViewAddresse: -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 peopleExamples:-IP address: 128.32.27.22-Name: [email protected] 4General ViewDifferentiating between names and addresses introduces several consistency problems:-What is a multicast IP address?-What is the IP address of a mobile host?-What is cnri.reston.va.us?Solution: interpret an address as just another name (that may happen to have location semantics)[email protected] 5Name ServiceName 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., bindings can be implemented by using tables)Resolution: procedure that, when invoked with a name, returns the corresponding valueName server: specific implementation of a resolution mechanism that is available on the network and that can be queried by sending [email protected] 6General ViewIn general there are multiple mappingsHost name: amber.berkeley.edu IP address: 128.32.27.22 Ethernet MAC address: 12.34.56.78.90.12 DNS resolutionARP (Address Resolution Protocol)[email protected] 7MappingMultiple names can map onto the same name at the underlying level-Example: www.berkeley.edu and amber.berkeley.edu can map to the same machine (I.e., the same IP address)One name can map onto multiple names at the underlying level-Example: www.yahoo.com can be mapped to multiple [email protected] 8Name Hierarchyrooteducomgov milorgnet uk [email protected] 9Name HierarchyUnique domain suffix is assigned by the Internet AuthorityThe domain administrators have complete control over the domainNo limit on the number of subdomains or number of levelsName 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] 10Top Level DomainsDomain Name Assignmentcom Commercialedu Educational gov Government mil Military net Network Org Other organizationsArpa Advances research project agencycountry code au, uk, [email protected] 11DNS Name ServersWhy not centralize DNS? -Single point of failure-Traffic volume-Distant centralized database-MaintenanceDoesn’t [email protected] 12Server Hierarchy: ZonesA zone corresponds to an administrative authority that is responsible for that portion of the hierarchyrooteducomgov milorgnet uk [email protected] 13Server HierarchyServer are organized in hierarchiesEach 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] 14Server HierarchyAuthority: each server has the name to address translation table for all names in the name space it controlsEvery server knows the rootRoot server knows about all top-level [email protected] 15DNS Name ServersNo server has all name-to-IP address mappingsLocal name servers:-Each ISP (company) has local (default) name server-Host DNS query first go to local name serverAuthoritative name servers:-For a host: stores that host’s IP address, name-Can perform name/address translation for that host’s [email protected] 16DNS: Root Name Servers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~ Dozen root name servers [email protected] 17Simple 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] 18DNS ExampleRoot name server:May not know authoritative name serverMay 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] 19DNS: Iterated QueriesRecursive query:Puts burden of name resolution on contacted name serverHeavy 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] 20DNS RecordsDNS: distributed database storing resource records (RR)Type=NS-name is domain (e.g. foo.com)-value is IP address of authoritative name server for this domainRR format: (name, value, type,ttl)Type=A-name is hostname-value is IP addressType=CNAME-name is an alias name for some “cannonical” (the real) name-value is cannonical nameType=MX-value is hostname of mailserver associated with [email protected] 21DNS protocol, messagesDNS protocol : query and reply messages, both with


View Full Document

Berkeley ELENG 122 - Domain Name Server - DNS

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 Server - DNS
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 Server - DNS 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 Server - DNS 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?