Scribd
Upload
118 views15 pages

Naming

This document discusses naming systems and provides examples of how names are used to identify different types of objects. It describes key properties of naming, such as names versus addresses and hierarchical versus flat naming schemes. The document also provides an overview of the Domain Name System (DNS) and how it uses a hierarchical name space and resource records stored on name servers to map names to IP addresses. Examples of DNS records for hosts, mail servers, and name servers are given. Distributed file systems are also discussed, along with examples of how names can provide location transparency.

Uploaded by

Sangeetha Bajanthri
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
118 views15 pages

Naming

This document discusses naming systems and provides examples of how names are used to identify different types of objects. It describes key properties of naming, such as names versus addresses and hierarchical versus flat naming schemes. The document also provides an overview of the Domain Name System (DNS) and how it uses a hierarchical name space and resource records stored on name servers to map names to IP addresses. Examples of DNS records for hosts, mail servers, and name servers are given. Distributed file systems are also discussed, along with examples of how names can provide location transparency.

Uploaded by

Sangeetha Bajanthri
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 15

Naming

Outline
Terminology
Domain Naming System
Distributed File Systems

Spring 2002

CS 461

Overview
What do names do?

identify objects
help locate objects
define membership in a group
specify a role
convey knowledge of a secret

Name space
defines set of possible names
consists of a set of name to value bindings
Spring 2002

CS 461

Properties

Names versus addresses


Location transparent versus location-dependent
Flat versus hierarchical
Global versus local
Absolute versus relative
By architecture versus by convention
Unique versus ambiguous
Spring 2002

CS 461

Examples
Hosts
[Link]
[Link]

[Link]

[Link]

Files
/usr/llp/tmp/foo

(server, fileid)

Users
Larry Peterson

Spring 2002

llp@[Link]

CS 461

Examples (cont)
Mailboxes

User
1
2
[Link] user @ [Link]
Mail
program

Name
server

[Link]

[Link]
3

TCP
[Link]

IP

Services
nearby ps printer with short queue and 2MB

Spring 2002

CS 461

Domain Naming System


Hierarchy
edu
princeton mit
cs

com

gov

mil

org

net

uk

fr

cisco yahoonasa nsf arpa navy acm ieee

ee physics

ux01ux04

Name
[Link]

Spring 2002

CS 461

Name Servers
Partition hierarchy into zones
edu
princeton mit
cs

com

gov

mil

org

net

uk

fr

cisco yahoonasa nsf arpa navy acm ieee

ee physics

ux01ux04
Root
name server

Each zone implemented by


two or more name servers

Princeton
name server

Cisco
name server

CS
EE

name server
name server

Spring 2002

CS 461

Resource Records
Each name server maintains a collection of resource records
(Name, Value, Type, Class, TTL)

Name/Value: not necessarily host names to IP addresses


Type
NS: Value gives domain name for host running name server that knows how
to resolve names within specified domain.
CNAME: Value gives canonical name for particle host; used to define aliases.
MX: Value gives domain name for host running mail server that accepts
messages for specified domain.

Class: allow other entities to define types


TTL: how long the resource record is valid

Spring 2002

CS 461

Root Server
([Link], [Link], NS, IN)
([Link], [Link], A, IN)
([Link], [Link], NS, IN)
([Link], [Link], A, IN)

Spring 2002

CS 461

Princeton Server
([Link], [Link], NS, IN)
([Link], [Link], A, IN)
([Link], [Link], NS, IN)
([Link], [Link], A, IN)
([Link], [Link], A, IN)
([Link], [Link], A, IN)
([Link], [Link], A, IN)
([Link], [Link], A, IN)

Spring 2002

CS 461

10

CS Server
([Link], [Link], MX, IN)
([Link], [Link], A, IN)
([Link], [Link],
CNAME, IN)
([Link], [Link], A, IN)
([Link], [Link],
CNAME, IN)
([Link], [Link], A, IN)
([Link], [Link],
CNAME, IN)

Spring 2002

CS 461

11

Name Resolution
Strategies
forward
iterative
recursive

Root
name
server
3

1
[Link]
Client
[Link]
8

4
Princeton
name
server

Local
name
server
5

Local server
need to know root at only one
place (not each host)
site-wide cache
Spring 2002
CS 461

CS
name
server

12

Distributed File Systems


No Transparency
Global AFS: /[Link]/usr/llp/tmp/foo
Windows: f:/usr/llp/tmp/foo

Transparency by Convention
NFS: /usr/llp/tmp/foo
Or Not: /n/fs/fac5/llp/tmp/foo

Transparency by Architecture
Sprite: /usr/llp/tmp/foo

Private versus Shared


ASF: /usr/llp/tmp/foo

Spring 2002

versus /afs/shared

CS 461

13

Example

a
e

b
g

Prefix Domain
/
1
/a/
2
/d/
3
/d/k/
4

i
l

j
m

k
n

p
q

Spring 2002

CS 461

s
14

Stupid Naming Tricks

Symbolic links and mount points


Per-User and logical name spaces
Computed directories
Load balancing and content distribution
Attribute-based names
Hash-based schemes

Spring 2002

CS 461

15

You might also like