1 2004.6.8.  This Class  Chapter 9  Next Class  Wrap up this semester  Demo/discuss programming assignments  Review what we have learned  Questionnaire/Feedback.

Slides:



Advertisements
Similar presentations
DNS – Domain Name system Converting domain names to IP addresses since 1983.
Advertisements

Domain Name System (or Service) (DNS) Computer Networks Computer Networks Term B10.
9/23/2003-9/25/2003 Sockets & DNS September 23-25, 2003.
Domain Name System (or Service) (DNS) Computer Networks Computer Networks Spring 2012 Spring 2012.
EEC-484/584 Computer Networks Lecture 5 Wenbing Zhao (Part of the slides are based on Drs. Kurose & Ross ’ s slides for their Computer.
2: Application Layer1 FTP, SMTP and DNS. 2: Application Layer2 FTP: separate control, data connections r FTP client contacts FTP server at port 21, specifying.
1 Domain Name System (DNS). 2 DNS: Domain Name System Internet hosts, routers: –IP address (32 bit) - used for addressing datagrams –“name”, e.g., gaia.cs.umass.edu.
1 K. Salah Module 2.2: Domain Name System IP assigns 32-bit addresses to hosts (interfaces) –Binary addresses easy for computers to manage –All applications.
2: Application Layer1 Chapter 2 Application Layer Computer Networking: A Top Down Approach, 4 th edition. Jim Kurose, Keith Ross Addison-Wesley, July 2007.
Application Layer session 1 TELE3118: Network Technologies Week 12: DNS Some slides have been taken from: r Computer Networking: A Top Down Approach.
2: Application Layer FTP, , and DNS. 2: Application Layer 2 Chapter 2 Application Layer Computer Networking: A Top Down Approach Featuring.
Computer Communication Digital Communication in the Modern World Application Layer cont. DNS, SMTP
1 An Overview of Applications Xin Liu ECS 152A Ref: slides by J. Kurose and K. Ross.
CPSC 441: DNS1 Instructor: Anirban Mahanti Office: ICT Class Location: ICT 121 Lectures: MWF 12:00 – 12:50 Notes derived.
Application Layer 2-1 Chapter 2 Application Layer Computer Networking: A Top Down Approach 6 th edition Jim Kurose, Keith Ross Addison-Wesley March 2012.
Name Resolution and DNS. Domain names and IP addresses r People prefer to use easy-to-remember names instead of IP addresses r Domain names are alphanumeric.
Electronic Mail Three major components: SMTP user agents mail servers
Chapter 2 Application Layer
2: Application Layer1 Chapter 2 Application Layer Computer Networking: A Top Down Approach 6 th edition Jim Kurose, Keith Ross Addison-Wesley March 2012.
NET0183 Networks and Communications Lecture 25 DNS Domain Name System 8/25/20091 NET0183 Networks and Communications by Dr Andy Brooks.
CS 4396 Computer Networks Lab
1 Domain Name System (DNS). 2 DNS: Domain Name System Internet hosts: – IP address (32 bit) - used for addressing datagrams – “name”, e.g.,
Domain Name System (DNS)
Data Communications and Computer Networks Chapter 2 CS 3830 Lecture 10 Omar Meqdadi Department of Computer Science and Software Engineering University.
2: Application Layer 1 Chapter 2: Application layer r 2.1 Principles of network applications r 2.2 Web and HTTP r 2.3 FTP r 2.4 Electronic Mail  SMTP,
05 - FTP, , and DNS 2: Application Layer.
DNS,SMTP,MIME.
21-1 Last time □ Finish HTTP □ FTP This time □ SMTP ( ) □ DNS.
2: Application Layer1 Chapter 2 Application Layer Computer Networking: A Top Down Approach Featuring the Internet, 2 nd edition. Jim Kurose, Keith Ross.
CS 471/571 Domain Name Server Slides from Kurose and Ross.
IT 424 Networks2 IT 424 Networks2 Ack.: Slides are adapted from the slides of the book: “Computer Networking” – J. Kurose, K. Ross Chapter 2: Application.
DNS: Domain Name System
Review: –Which protocol is used to move messages around in the Internet? –Describe how a message is moved from the sender’s UA to the receiver’s.
1 DNS: Domain Name System People: many identifiers: m SSN, name, Passport # Internet hosts, routers: m IP address (32 bit) - used for addressing datagrams.
Chapter 2 Application Layer Computer Networking: A Top Down Approach, 5 th edition. Jim Kurose, Keith Ross Addison-Wesley, April A note on the use.
1 Application Layer Lecture 6 Imran Ahmed University of Management & Technology.
DNS: Domain Name System People: many identifiers: – SSN, name, Passport # Internet hosts, routers: – IP address (32 bit) - used for addressing datagrams.
Lecture 6: Video Streaming 2-1. Outline  Network basics:  HTTP protocols  Studies on HTTP performance from different views:  Browser types [NSDI 2014]
25.1 Chapter 25 Domain Name System Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
1 DNS: Domain Name System People: many identifiers: m SSN, name, Passport # Internet hosts, routers: m IP address (32 bit) - used for addressing datagrams.
CSE 524: Lecture 5 Application layer protocols. Where we’re at… ● Internet architecture and history ● Internet protocols in practice ● Application layer.
Internet and Intranet Protocols and Applications Lecture 5 Application Protocols: DNS February 20, 2002 Joseph Conron Computer Science Department New York.
2: Application Layer1 DNS: Domain Name System People have many identifiers: SSN, name, passport number Internet hosts, routers have identifiers, too: IP.
CPSC 441: DNS 1. DNS: Domain Name System Internet hosts: m IP address (32 bit) - used for addressing datagrams m “name”, e.g., - used by.
CS 3830 Day 10 Introduction 1-1. Announcements r Quiz #2 this Friday r Program 2 posted yesterday 2: Application Layer 2.
EE 122: Lecture 20 (Domain Name Server - DNS) Ion Stoica Nov 15, 2001 (* based on the some on-line slides of J. Kurose & K. Rose and of Raj Jain)
Lecture 5: Web Continued 2-1. Outline  Network basics:  HTTP protocols  Studies on HTTP performance from different views:  Browser types [NSDI 2014]
Chapter 2 Application Layer Computer Networking: A Top Down Approach, 4 th edition. Jim Kurose, Keith Ross Addison-Wesley, July 2007.
2: Application Layer 1 Chapter 2: Application layer r 2.1 Principles of network applications r 2.2 Web and HTTP r 2.3 FTP r 2.4 Electronic Mail  SMTP,
Application Layer 2-1 Chapter 2 Application Layer Computer Networking: A Top Down Approach 6 th edition Jim Kurose, Keith Ross Addison-Wesley March 2012.
COMP 431 Internet Services & Protocols
Application Layer, 2.5 DNS 2-1 Chapter 2 Application Layer Computer Networking: A Top Down Approach 6 th edition Jim Kurose, Keith Ross Addison-Wesley.
Networking (Cont’d). Congestion Control l Is achieved by informing nodes along a route that congestion has occurred and asking them to reduce their packet.
Important r On Friday, could you ask students to please me their groups (one per group) for Project 2 so we can assign IP addresses. I’ll send.
CSEN 404 Application Layer II Amr El Mougy Lamia Al Badrawy.
Spring 2006 CPE : Application Layer_DNS 1 Special Topics in Computer Engineering Application layer: Domain Name System Some of these Slides are.
@Yuan Xue A special acknowledge goes to J.F Kurose and K.W. Ross Some of the slides used in this lecture are adapted from their.
@Yuan Xue A special acknowledge goes to J.F Kurose and K.W. Ross Some of the slides used in this lecture are adapted from their.
Introduction to Networks
Session 6 INST 346 Technologies, Infrastructure and Architecture
Chapter 9: Domain Name Servers
Introduction to Communication Networks
Chapter 7: Application layer
Cookies, Web Cache & DNS Dr. Adil Yousif.
CSE 4213: Computer Networks II
DNS: Domain Name System
FTP, SMTP and DNS 2: Application Layer.
Lecture 3 – Chapter 2 CIS 5617, Fall 2019 Anduo Wang
Presentation transcript:

 This Class  Chapter 9  Next Class  Wrap up this semester  Demo/discuss programming assignments  Review what we have learned  Questionnaire/Feedback  Final exam tips

2 Applications  DNS  SMTP, MIME, IMAP  HTTP  SNMP  RTP  SDP, SIP, H.323

3 DNS: Domain Name System People: many identifiers:  SSN, name, passport # Internet hosts, routers:  IP address (32 bit) - used for addressing datagrams  “name”, e.g., gaia.cs.umass.edu - used by humans Q: map between IP addresses and name ? Domain Name System:  distributed database implemented in hierarchy of many name servers  application-layer protocol host, routers, name servers to communicate to resolve names (address/name translation)  note: core Internet function, implemented as application-layer protocol  complexity at network’s “edge”

4 DNS 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 goes to local name server authoritative name server:  for a host: stores that host’s IP address, name  can perform name/address translation for that host’s name Why not centralize DNS?  single point of failure  traffic volume  distant centralized database  maintenance doesn’t scale!

5 DNS: 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 b USC-ISI Marina del Rey, CA l ICANN Marina del Rey, CA e NASA Mt View, CA f Internet Software C. Palo Alto, CA i NORDUnet Stockholm k RIPE London m WIDE Tokyo a NSI Herndon, VA c PSInet Herndon, VA d U Maryland College Park, MD g DISA Vienna, VA h ARL Aberdeen, MD j NSI (TBD) Herndon, VA 13 root name servers worldwide

6 Simple DNS example host surf.eurecom.fr wants IP address of gaia.cs.umass.edu 1. contacts its local DNS server, dns.eurecom.fr 2. dns.eurecom.fr contacts root name server, if necessary 3. root name server contacts authoritative name server, dns.umass.edu, if necessary requesting host surf.eurecom.fr gaia.cs.umass.edu root name server authorititive name server dns.umass.edu local name server dns.eurecom.fr

7 DNS example Root name server:  may not know authoritative name server  may know intermediate name server: who to contact to find authoritative name server requesting host surf.eurecom.fr gaia.cs.umass.edu root name server local name server dns.eurecom.fr authoritative name server dns.cs.umass.edu intermediate name server dns.umass.edu 7 8

8 DNS: iterated queries recursive 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 host surf.eurecom.fr gaia.cs.umass.edu root name server local name server dns.eurecom.fr authoritative name server dns.cs.umass.edu intermediate name server dns.umass.edu 7 8 iterated query

9 DNS: caching and updating records  once (any) name server learns mapping, it caches mapping  cache entries timeout (disappear) after some time  update/notify mechanisms under design by IETF  RFC 2136  charter.html

10 DNS records DNS: distributed db storing resource records (RR)  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)  Type=A  name is hostname  value is IP address  Type=CNAME  name is alias name for some “canonical” (the real) name is really servereast.backup2.ibm.com  value is canonical name  Type=MX  value is name of mailserver associated with name

11 DNS protocol, messages DNS protocol : query and reply messages, both with same message format msg header  identification: 16 bit # for query, reply to query uses same #  flags:  query or reply  recursion desired  recursion available  reply is authoritative

12 DNS protocol, messages Name, type fields for a query RRs in response to query records for authoritative servers additional “helpful” info that may be used

13 Questions on DNS  Refer to root name server every time you type in an address out of your domain?  TCP or UDP?

14 Points of Distinction  Application protocols vs programs  Applicaton protocols vs data format  SMTP vs ??  HTTP vs ??  SNMP vs ??

15 SMTP HELO cs.princeton.edu 250 Hello MAIL FROM: 250 OK RCPT TO: 250 OK RCPT TO: 550 No such user here DATA 354 Start mail input; end with..xxxxxxxxx. 250 OK QUICK 221 Closing connection

16 HTTP  Operations  OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE, CONNECT  Response Messages  1xx - Informational  2xx - Success  3xx - Redirection  4xx - Client error  5xx - Server error

17 SNMP (I) Managing entity Managed device Managed device data Simple Network Management Protocol Agent

18 SNMP (2)  Evolution of SNMP  v1 - Get, GetNext, Set  v2 - Get, GetNext, GetBulk, Set, Inform  v3 - security and administration capabilities  Limitations: overhead per MIB, unreliable transfer, CPU overload  Data = MIB (Management Information Base)  In Structure of Management Information language  Defines counters at managed device

19 RTP  Functionalities common to multimedia applications?  interoperate between 2 end hosts  determine timing relationship in data  recover synchronization  indicate packet loss  indicate frame boundary  include user-friendly sender identity  efficient use of bandwidth

20 Real-time Transport Control Protocol  Main functions  Feedback on application's performance  Correlate and synchronize different media streams  Convey sender identity for display

21 Session/Call Control - SIP cisco.com proxy princeton.edu proxy mypc.cisco.comyourpc.princeton.edu

22 H.323  ITU recommendation  Popular protocol for Internet telephony  H.323 terminals talk to each other  Or use a H.323 gateway to connect to PSTN

23 Acknowledgments  Some slides are from:  Computer Networking: A Top Down Approach Featuring the Internet, 2 nd edition. Jim Kurose, Keith Ross Addison-Wesley, July All material copyright J.F Kurose and K.W. Ross, All Rights Reserved