1. CPSC 441: DNS1 Instructor: Anirban Mahanti Office: ICT 745 Email: mahanti@cpsc.ucalgary.ca Class Location: ICT 121 Lectures: MWF 12:00 – 12:50 Notes derived from “ Computer Networking: A Top Down Approach Featuring the Internet”, 2005, 3 rd edition, Jim Kurose, Keith Ross, Addison-Wesley. Slides are adapted from the companion web site of the book, as modified by Anirban Mahanti (and Carey Williamson). Domain Name System (DNS)

2. CPSC 441: DNS2 DNS: Domain Name System Internet hosts: m IP address (32 bit) - used for addressing datagrams m “name”, e.g., ww.yahoo.com - used by humans DNS: provides translation between host name and IP address m distributed database implemented in hierarchy of many name servers m Distributed for scalability & reliability

3. CPSC 441: DNS3 DNS Services r Hostname to IP address translation r Host aliasing m Canonical and alias names r Mail server aliasing r Load distribution m Replicated Web servers: set of IP addresses for one canonical name

4. CPSC 441: DNS4 requesting host cis.poly.edu gaia.cs.umass.edu root DNS server local DNS server dns.poly.edu 1 2 3 4 5 6 authoritative DNS server dns.cs.umass.edu 7 8 TLD DNS server DNS Infrastructure r Host at cis.poly.edu wants IP address for gaia.cs.umass.edu r Infrastructure: m Client resolver m Local DNS server m Authoritative DNS Server m Root DNS Server m Top-Level Domain DNS Server

5. CPSC 441: DNS5 Distributed, Hierarchical Database r Root servers and TLD servers typically do not contain hostname to IP mappings; they contain mappings for locating authoritative servers. Root DNS Servers com DNS servers ca DNS serversedu DNS servers poly.edu DNS servers umass.edu DNS servers yahoo.com DNS servers amazon.com DNS servers ucalgary.ca DNS servers TLD Servers usask.ca DNS servers

6. CPSC 441: DNS6 DNS: Root name servers r contacted by local name server that can not resolve name r root name server: m contacts authoritative name server if name mapping not known m gets mapping m returns mapping to local name server

7. CPSC 441: DNS7 TLD and Authoritative Servers r Top-level domain (TLD) servers: responsible for com, org, net, edu, etc, and all top-level country domains uk, fr, ca, jp. m Network solutions maintains servers for com TLD m Educause for edu TLD r Authoritative DNS servers: organization’s DNS servers, providing authoritative hostname to IP mappings for organization’s servers (e.g., Web and mail). m Can be maintained by organization or service provider

8. CPSC 441: DNS8 Local Name Server r Each ISP (residential ISP, company, university) has one. m Also called “default name server” r When a host makes a DNS query, query is sent to its local DNS server m Acts as a proxy, forwards query into hierarchy. m Reduces lookup latency for commonly searched hostnames

9. CPSC 441: DNS9 requesting host cis.poly.edu gaia.cs.umass.edu root DNS server local DNS server dns.poly.edu 1 2 4 5 6 authoritative DNS server dns.cs.umass.edu 7 8 TLD DNS server 3 Recursive queries recursive query: r puts burden of name resolution on contacted name server r heavy load? iterated query: r contacted server replies with name of server to contact r “I don’t know this name, but ask this server”

10. CPSC 441: DNS10 DNS: caching and updating records r once (any) name server learns mapping, it caches mapping m cache entries timeout (disappear) after some time m TLD servers typically cached in local name servers Thus root name servers not often visited r update/notify mechanisms under design by IETF m RFC 2136 m http://www.ietf.org/html.charters/dnsind-charter.html

11. CPSC 441: DNS11 DNS records DNS: distributed db storing resource records (RR) r Type=NS  name is domain (e.g. foo.com)  value is IP address of authoritative name server for this domain RR format: (name, value, type, ttl) r Type=A  name is hostname  value is IP address r Type=CNAME  name is alias name for some “cannonical” (the real) name www.ibm.com is really servereast.backup2.ibm.com  value is cannonical name r Type=MX  value is name of mailserver associated with name

12. CPSC 441: DNS12 DNS protocol, messages DNS protocol : query and reply messages, both with same message format msg header r identification: 16 bit # for query, reply to query uses same # r flags: m query or reply m recursion desired m recursion available m reply is authoritative

13. CPSC 441: DNS13 DNS protocol, messages Name, type fields for a query RRs in reponse to query records for authoritative servers additional “helpful” info that may be used

14. CPSC 441: DNS14 Inserting records into DNS r Example: just created startup “Network Utopia” r Register name networkuptopia.com at a registrar (e.g., Network Solutions) m Need to provide registrar with names and IP addresses of your authoritative name server (primary and secondary) m Registrar inserts two RRs into the com TLD server: (networkutopia.com, dns1.networkutopia.com, NS) (dns1.networkutopia.com, 212.212.212.1, A) r Put in authoritative server Type A record for www.networkuptopia.com and Type MX record for networkutopia.com r How do people get the IP address of your Web site?

15. CPSC 441: DNS15 Application Layer: Summary r Application architectures m client-server m P2P m hybrid r application service requirements: m reliability, bandwidth, delay r Internet transport service model m connection-oriented, reliable: TCP m unreliable, datagrams: UDP Our study of network apps now complete! r specific protocols: m HTTP m FTP m SMTP, POP, IMAP m DNS r socket programming (assignment two + tutorial sessions)

16. CPSC 441: DNS16 Application Layer: Summary r typical request/reply message exchange: m client requests info or service m server responds with data, status code r message formats: m headers: fields giving info about data m data: info being communicated Most importantly: learned about protocols r control vs. data msgs m in-band, out-of-band r centralized vs. decentralized r stateless vs. stateful r reliable vs. unreliable msg transfer r “complexity at network edge”