DNS •DNS Design •DN dDNS Today

[Pages:11]15-441 Lecture 7

DNS

Lecture 13

Copyright ? Seth Goldstein, 2008

Based on slides from previous 441 lectures

15-441 ? 2008

1

Lecture 13

Outline

?DNS Design ?DNS Today

(Extra credit, remind me at end)

15-441 ? 2008

2

What is DNS?

? DNS (Domain Name Service) is primarily used to translate human readable names into machine usable addresses, e.g., IP addresses.

?DNS goal: ? Efficiently locate resources. E.g., Map name ? IP address ? Scale to many users over a large area ? Scale to many updates

Lecture 13

15-441 ? 2008

3

How resolve name ? IP addr?

Lecture 13

15-441 ? 2008

4

Obvious Solutions (1)

Why not centralize DNS? ?Single point of failure ?Traffic volume ?Distant centralized database ?Single point of update

?Doesn't scale!

Lecture 13

15-441 ? 2008

Obvious Solutions (2)

Why not use /etc/hosts?

?Original Name to Address Mapping

? Flat namespace

? /etc/hosts

? SRI kept main copy

? Downloaded regularly

?Mid 80's this became untenable. Why?

?Count of hosts was increasing: machine per domain ? machine per user

? Many more downloads ? Many more updates

/etc/hosts still exists.

5

Lecture 13

15-441 ? 2008

6

Domain Name System Goals

?Basically a wide-area distributed database (The biggest in the world!)

? Scalability

?Decentralized maintenance

? Robustness

?Global scope

? Names mean the same thing everywhere

?Don't need all of ACID

? Atomicity

? Strong consistency

?Do need: distributed update/query & Performance

Lecture 13

15-441 ? 2008

7

Programmer's View of DNS

? Conceptually, programmers can view the DNS database as a collection of millions of host entry structures:

/* DNS host entry structure */

struct hostent {

char *h_name;

/* official domain name of host */

char **h_aliases; /* null-terminated array of domain names */

int h_addrtype; /* host address type (AF_INET) */

int h_length;

/* length of an address, in bytes */

char **h_addr_list; /* null-termed array of in_addr structs */

};

? in_addr is a struct consisting of 4-byte IP addr ? Functions for retrieving host entries from DNS:

? gethostbyname: query key is a DNS host name. ? gethostbyaddr: query key is an IP address.

Lecture 13

15-441 ? 2008

8

DNS Message Format

DNS Header Fields

? Identification

Identification

Flags

? Used to match up request/response

12 bytes

No. of Questions

No. of Answer RRs

? Flags

No. of Authority RRs

No. of Additional RRs

? 1-bit to mark query or response

Name, type fields for a query

RRs in response to query

Questions (variable number of answers) Answers (variable number of resource records)

? 1-bit to mark authoritative or not ? 1-bit to request recursive resolution ? 1-bit to indicate support for recursive

Records for authoritative servers

Authority (variable number of resource records)

resolution

Additional "helpful info that may be used

Additional Info (variable number of resource records)

Lecture 13

15-441 ? 2008

9

Lecture 13

15-441 ? 2008

10

DNS Records

RR format: (class, name, value, type, ttl)

? DB contains tuples called resource records (RRs)

? Classes = Internet (IN), Chaosnet (CH), etc. ? Each class defines value associated with type

For "IN" class:

? Type=A

? Type=CNAME

? name is hostname ? value is IP address

? Type=NS ? name is domain (e.g. ) ?

? value is name of authoritative name server for this domain

? name is an alias name for some "canonical" name

? value is canonical name

Type=MX

? value is hostname of mailserver associated with name

Lecture 13

15-441 ? 2008

11

Properties of DNS Host Entries

Different kinds of mappings are possible:

?1-1 mapping between domain name and IP addr:

provolone.crcl.cs.cmu.edu maps to 128.2.218.81

?Multiple domain names maps to the same IP addr:

scs.cmu.edu and cs.cmu.edu both map to 128.2.203.164

?Single domain name maps to multiple IP addresses: and map to multiple IP addrs.

?Some valid domain names don't map to any IP addr: crcl.cs.cmu.edu doesn't have a host

Lecture 13

15-441 ? 2008

12

DNS Design: Hierarchy Definitions

root

org net edu com uk gwu ucb cmu bu mit cs ece crcl

? Each node in hierarchy stores a list of names that end with same suffix ? Suffix = path up tree

? E.g., given this tree, where would following be stored: ? ? Fred.edu ? Fred.cmu.edu ? Fred.crcl.cs.cmu.edu ? Fred.cs.mit.edu

Lecture 13

15-441 ? 2008

13

DNS Design: Zone Definitions

root

org net edu com uk gwu ucb cmu bu mit cs ece crcl

? Zone = contiguous section of name space ? E.g., Complete tree, single node or subtree

? A zone has an associated set of name servers ? Must store list of names and tree links

Subtree Single node

Complete Tree

Lecture 13

15-441 ? 2008

14

DNS Design: Cont.

DNS: Root Name Servers

?Zones are created by convincing owner node to create/delegate a subzone

? Records within zone stored in multiple redundant name servers

? Primary/master name server updated manually

? Secondary/redundant servers updated by zone transfer of name space

? Zone transfer is a bulk transfer of the "configuration" of a DNS server ? uses TCP to ensure reliability

? Example:

? CS.CMU.EDU created by CMU.EDU admins

? Who creates CMU.EDU or .EDU?

? Responsible for "root" zone

? 13 root name servers

? Currently {a-m}.root-

? Local name servers contact root servers when they cannot resolve a name

? Why 13?

Lecture 13

15-441 ? 2008

15

Lecture 13

15-441 ? 2008

16

Not really 13!

So Far

?Database structure

? Hierarchy of labels x.y.z

? Organized into zones

? Zones have nameservers (notice plural!)

?Database layout

? Records which map names?names, names?ip,

etc.

?Programmer API: gethostbyname, ...

Check out anycast)

10/08, from root-

Lecture 13

15-441 ? 2008

17

Lecture 13

15-441 ? 2008

18

Servers/Resolvers

?Each host has a resolver ? Typically a library that applications can link to ? Local name servers hand-configured (or DHCP) (e.g. /etc/resolv.conf)

?Name servers ? Either responsible for some zone or... ? Local servers

? Do lookup of distant host names for local hosts ? Typically answer queries about local zone

Lecture 13

15-441 ? 2008

19

Typical Resolution

cs.cmu.edu

root & edu DNS server

Client

Local DNS server

ns1.cmu.edu DNS server

ns1.cs.cmu.edu DNS server

Hmm: Notice root server returned NS ns1.cmu.edu

Lecture 13

15-441 ? 2008

20

Typical Resolution

?Steps for resolving cmu.edu

? Application calls gethostbyname() (RESOLVER)

? Resolver contacts local name server (S1) ? S1 queries root server (S2) for (cmu.edu) ? S2 returns NS record for cmu.edu (S3) ? What about A record for S3?

? This is what the additional info section is for (PREFETCHING)

? S1 queries S3 for cmu.edu ? S3 returns A record for cmu.edu

?Can return multiple A records ? What does this mean?

Lecture 13

15-441 ? 2008

21

Lookup Methods

Recursive query:

? Server goes out and searches for more info

? Only returns final answer or "not found"

root name server 2 iterated query

3 4

Iterative query:

? Server responds with as much as it knows.

? "I don't know this name, but ask this server"

local name server dns.eurecom.fr

18

7

intermediate name server

dns.umass.edu

5

6 authoritative name

server

dns.cs.umass.edu

requesting host

surf.eurecom.fr

Workload impact on choice?

? Root/distant server does iterative

? Local server typically does recursive

Lecture 13

15-441 ? 2008

gaia.cs.umass.edu

22

How to manage workload?

?Does root nameserver do recursive lookups? ?What about other zones? ?What about imbalance in popularity?

? .com versus .dj ? versus bleu.crcl.cs.cmu.edu? ?How do we scale query workload?

Workload and Caching

?DNS responses are cached

? Quick response for repeated translations ? Other queries may reuse some parts of lookup

? E.g., NS records for domains

?DNS negative queries are cached

? Don't have to repeat past mistakes ? E.g., misspellings, search strings in resolv.conf

?How do you handle updates?

Lecture 13

15-441 ? 2008

23

Lecture 13

15-441 ? 2008

24

Workload and Caching

?DNS responses are cached

? Quick response for repeated translations ? Other queries may reuse some parts of lookup

? E.g., NS records for domains

?DNS negative queries are cached

? Don't have to repeat past mistakes ? E.g., misspellings, search strings in resolv.conf

?Cached data periodically times out

? Lifetime (TTL) of data controlled by owner of data ? TTL passed with every record

Lecture 13

15-441 ? 2008

25

Typical Resolution

cs.cmu.edu

Client

Local DNS server

Lecture 13

15-441 ? 2008

root & edu DNS server

ns1.cmu.edu DNS server ns1.cs.cmu.edu

DNS server

26

Subsequent Lookup Example

ftp.cs.cmu.edu

Client

Local DNS server

Lecture 13

15-441 ? 2008

root & edu DNS server

cmu.edu DNS server cs.cmu.edu

DNS server

27

Reliability

?DNS servers are replicated

? Name service available if one replica is up ? Queries can be load balanced between replicas

?UDP used for queries

? Need reliability ? must implement this on top of UDP! ? Why not just use TCP?

?Try alternate servers on timeout

? Exponential backoff when retrying same server

?Same identifier for all queries

? Don't care which server responds

Lecture 13

15-441 ? 2008

28

So far

?Hierarchial name space

Lecture 13

15-441 ? 2008

Reverse DNS

Arpa: backronym ? Address and Routing Parameter Area

unnamed root

? Task

? Given IP address, find its name

arpa

edu

? Method

in-addr

cmu

? Maintain separate hierarchy based on IP names

128

cs

? Write 128.2.204.27 as 27.204.2.128.in-addr.arpa

? Why is the address reversed?

2 crcl

204

? Managing

? Authority manages IP addresses assigned to it

bleu

27

128.2.204.27

? E.g., CMU manages name space 2.128.in-addr.arpa

29

Lecture 13

15-441 ? 2008

30

.arpa Name Server Hierarchy

in-addr.arpa a.root- ? ? ? m.root-

chia.

128

(dill, henna, indigo, epazote, figwort, ginseng)

cucumber.srv.cs.cmu.edu,

2

t-.cmu.edu

t-.cmu.edu

mango.srv.cs.cmu.edu

204

(peach, banana, blueberry)

bleu 128.2.204.27

? At each level of hierarchy, have group of servers that are authorized to handle that region of hierarchy

Lecture 13

15-441 ? 2008

31

Prefetching

?Name servers can add additional data to response ?Why would they?

Lecture 13

15-441 ? 2008

32

 ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download