Names & Addresses. Names & Addresses. Names vs. Addresses. Identity. Names vs. Addresses. CS 194: Distributed Systems: Naming



Similar documents
CS 348: Computer Networks. - DNS; 22 nd Oct Instructor: Sridhar Iyer IIT Bombay

INTERNET DOMAIN NAME SYSTEM

The Domain Name System (DNS)

Application-layer protocols

NET0183 Networks and Communications

The Domain Name System (DNS)

Domain Name System (or Service) (DNS) Computer Networks Term B10

Domain Name System Richard T. B. Ma

CS3600 SYSTEMS AND NETWORKS

How To Map Between Ip Address And Name On A Domain Name System (Dns)

DNS: Domain Name System

Names vs. Addresses. Flat vs. Hierarchical Space. Domain Name System (DNS) Computer Networks. Lecture 5: Domain Name System

CS 355. Computer Networking. Wei Lu, Ph.D., P.Eng.

Overview of Computer Networks

Domain Name System (DNS) RFC 1034 RFC

Lecture 2 CS An example of a middleware service: DNS Domain Name System

DNS: Domain Names. DNS: Domain Name System. DNS: Root name servers. DNS name servers

CMPE 80N: Introduction to Networking and the Internet

Chapter 9: Name Services. 9.1 Introduction 9.2 Name services and the DNS 9.3 Directory services 9.6 Summary

Distributed Systems. 09. Naming. Paul Krzyzanowski. Rutgers University. Fall 2015

Naming. Name Service. Why Name Services? Mappings. and related concepts

Network Layers. CSC358 - Introduction to Computer Networks

web hosting and domain names

DNS Domain Name System

Outline. Definition. Name spaces Name resolution Example: The Domain Name System Example: X.500, LDAP. Names, Identifiers and Addresses

Domain Name System (DNS)

CS 43: Computer Networks Naming and DNS. Kevin Webb Swarthmore College September 17, 2015

Domain Name System DNS

Internet-Praktikum I Lab 3: DNS

Application. Transport. Network. Data Link. Physical. Network Layers. Goal

Application Protocols in the TCP/IP Reference Model

Motivation. Domain Name System (DNS) Flat Namespace. Hierarchical Namespace

DNS Domain Name System

Application Protocols in the TCP/IP Reference Model. Application Protocols in the TCP/IP Reference Model. DNS - Concept. DNS - Domain Name System

Application Protocols in the TCP/IP Reference Model. Application Protocols in the TCP/IP Reference Model. DNS - Domain Name System

FTP: the file transfer protocol

Naming and the DNS. Focus. How do we name hosts etc.? Application Presentation Topics. Session Domain Name System (DNS) /URLs

Understand Names Resolution

Domain Name Service (DNS) Training Division, NIC New Delhi

Domain Name System (DNS)

Introduction to Network Operating Systems

The Application Layer: DNS

Introduction to the Domain Name System

Domain Name System Security

Chapter 25 Domain Name System Copyright The McGraw-Hill Companies, Inc. Permission required for reproduction or display.

DATA COMMUNICATOIN NETWORKING

Computer Networks: Domain Name System

Part 5 DNS Security. SAST01 An Introduction to Information Security Martin Hell Department of Electrical and Information Technology

CS3250 Distributed Systems

Chapter 24 The Domain Name System (DNS)

Chapter 2 Application Layer

Computer Networks & Security 2014/2015

CS640: Computer Networks. Naming /ETC/HOSTS

Chapter 23 The Domain Name System (DNS)

HW2 Grade. CS585: Applications. Traditional Applications SMTP SMTP HTTP 11/10/2009

DNS and P2P File Sharing

Domain Name System (DNS)

Introduction to Web Design & Computer Principles CSCI-UA 4. Web Hosting and Domain Names

Applications & Application-Layer Protocols: The Domain Name System and Peerto-Peer

Domain Name System (DNS) Reading: Section in Chapter 9

DNS: Domain Name System

Domain Name System Submitted in partial fulfillment of the requirement for the award of degree of Computer Science

DNS : Domain Name System

1. Domain Name System

Computer Networks Prof. S. Ghosh Department of Computer Science and Engineering Indian Institute of Technology, Kharagpur Lecture - 34 DNS & Directory

The Domain Name System

3. The Domain Name Service

Agenda. Distributed System Structures. Why Distributed Systems? Motivation

Conquering the Challenges of IP Network Management with DHCP and DNS

TCP/IP works on 3 types of services (cont.): TCP/IP protocols are divided into three categories:

ARP and DNS. ARP entries are cached by network devices to save time, these cached entries make up a table

DNS Basics. DNS Basics

Internetworking with TCP/IP Unit 10. Domain Name System

Domain Name System. DNS is an example of a large scale client-server application. Copyright 2014 Jim Martin

DNS and BIND. David White

Domain Name System. Heng Sovannarith

- Domain Name System -

How to Install the Active Directory Domain Services (AD DS) Role in Windows Server 2008 R2 and Promote a Server to a Domain Controller

How do I get to

Implementing Domain Name Service (DNS)

DNS and issues in connecting UNINET-ZA to the Internet

The Domain Name System

IP addresses have hierarchy (network & subnet) Internet names (FQDNs) also have hierarchy. and of course there can be sub-sub-!!

Networking Domain Name System

416 Distributed Systems. Feb 24, 2016 DNS and CDNs

EECS 489 Winter 2010 Midterm Exam

Chapter 7 Implementing Domain Name System (DNS)

Transcription:

Names & Addresses CS 9: Distributed Systems: Naming Computer Science Division Department of Electrical Engineering and Computer Sciences University of California, Berkeley Berkeley, CA 970-77 What is a? What is an address? What is the difference between s and addresses? EECS - UCB Names & Addresses Names vs. Addresses Name: string of bits that refer to an entity E.g., your Address: string of bits that have location semantics E.g., your home address, your phone # Voyager address Seven-of-Nine Borg Weather a string is is a or or address may depend on context Names vs. Addresses Identity address Florence Name that uniquely identify an entity E.g., your SSN Identifier properties: An identifier refers to at most one entity Each entity is referred to by at most one identifier An identifier always refers to the same entity (i.e., it is never reused) Leonardo da Vinci City of Vinci

Addresses: Internet Centric View Says how to reach an object it has location semantics associated to it Usually, a format easy to process by computers Name: Does not have any location semantics associated to it Usually, a format easier to understand/read/remember by people Examples: IP address: 9.9..09 Name: arachne.berkeley.edu Name Service Name space: define the set of possible s and their relationship Hierarchical (e.g., Unix and Windows file s) Flat Bindings: the mapping between s and values (e.g., addresses or other s) Bindings can be implemented by using tables Resolution: procedure that, when invoked with a, 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 messages Binding and Resolution in the Internet In general there are multiple mappings Host : arachne.berkeley.edu DNS resolution IP address: 9.9..09 ARP (Address Resolution Protocol) Ethernet MAC address:...78.90. Mapping Multiple s can map onto the same address Example: and arachne.berkeley.edu maps to the same machine (i.e., the same IP address) One can map onto multiple addresses Example: www.yahoo.com can be mapped to multiple machines Name Space Linking and Mounting () A general naming graph with a single root node directory node Named entity Symbolic link in a naming graph

Linking and Mounting () Mounting remote spaces through a specific process protocol Linking and Mounting () Organization of the DEC Global Name Service Domain Name System (DNS) Hierarchy() root edu com gov mil org net uk fr berkeley cmu eecs sims sonoma DNS 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 could be a domain or an individual objects DNS Top Level Domains DNS Name Servers Domain Name com edu gov mil net org country code Assignment Commercial Educational Government Military Network Other organizations au, uk, ca, Why not centralize DNS? Single point of failure Traffic volume Distant centralized database Maintenance Doesn t scale!

Server Hierarchy: Zones A zone corresponds to an administrative authority that is responsible for that portion of the hierarchy berkeley root edu com gov mil org net uk fr cmu Server Hierarchy Server are organized in hierarchies Each server has authority over a portion of the hierarchy A single node in the hierarchy cannot be split A server maintains only a subset of all s It needs to know other servers that are responsible for the other portions of the hierarchy eecs sims divine Server Hierarchy Authority: each server has the to address translation table for all s in the space it controls Every server knows the root Root server knows about all top-level domains DNS Name Servers No server has all -to-ip address mappings Local servers: Each ISP (company) has local (default) server Host DNS query first go to local server Authoritative servers: For a host: stores that host s (, IP address) Can perform /address translation for that host s DNS: Root Name Servers Simple DNS Example Contacted by local server that can not resolve Root server: Contacts authoritative server if mapping not known Gets mapping Returns mapping to local server ~ Dozen root servers worldwide Host whsitler.cs.cmu.edu wants IP address of. Contacts its local DNS server,. contacts root server, if necessary. Root server contacts authoritative server, ns.berkeley.edu, if necessary root server local server authorititive server ns.berkeley.edu

Root server: May not know authoritative server May know intermediate server: who to contact to find authoritative server? DNS Example local server 8 root server 7 intermediate server (edu server) authoritative server ns.berkeley.edu Recursive query: Puts burden of resolution on contacted server Heavy load? DNS: Iterated Queries Iterated query: local server Contacted server replies with of server to contact 8 I don t know this, but ask this server root server iterated query intermediate server (edu server) 7 authoritative server ns.berkeley.edu