Lecture 4: Basic Internet Operations

Similar documents
Networking Applications

Testing IPv6 address records in the DNS root

DNS. David Malone. 19th October 2004

The Domain Name System

INSTITUT NATIONAL DES TELECOMMUNICATIONS. MSc Computer and Communication Networks MSc Information Technology Final Examination

K-Root Nameserver Operations

Preparation Test AAAA and EDNS0 support Share Your Results Results Reported Testing Period

K-Root Name Server Operations

Advanced Networking. Domain Name System

Advanced Networking. Domain Name System. Purpose of DNS servers. Purpose of DNS servers. Purpose of DNS servers

Root DNS Anycast in South Asia

f.root-servers.net ISOC cctld Workshop Nairobi, Kenya, 2005

The Domain Name System

CompSci 356: Computer Network Architectures. Lecture 20: Domain Name System (DNS) and Content distribution networks Chapter 9.3.1

IPv6 Support in the DNS. Athanassios Liakopoulos 6DEPLOY IPv6 Training, Skopje, June 2011

The net and it s Ecosystem

CS615 - Aspects of System Administration

Objectives. Upon completion you will be able to:

More Internet Support Protocols

Chapter 19. Domain Name System (DNS)

Domain Name System (DNS)

CS615 - Aspects of System Administration

CS519: Computer Networks. Lecture 6: Apr 5, 2004 Naming and DNS

Linux Network Administration

CSC 574 Computer and Network Security. DNS Security

DNS and BIND Rock Eagle Computing Conference October 27, 2000 CL 10/25/00

Interested in learning more? Global Information Assurance Certification Paper. Copyright SANS Institute Author Retains Full Rights

Domain Name System.

Lecture 4: The Transport Layer and UDP

CSE 127 Computer Security

IP ADDRESSES, NAMING, AND DNS

Prof. Shervin Shirmohammadi SITE, University of Ottawa. Internet Protocol (IP) Lecture 2: Prof. Shervin Shirmohammadi CEG

CSE 123: Computer Networks

ICS 351: Networking Protocols

ECE 650 Systems Programming & Engineering. Spring 2018

Top-Down Network Design

Communications Software. CSE 123b. CSE 123b. Spring Lecture 11: Domain Name System (DNS) Stefan Savage. Some pictures courtesy David Wetherall

CSE 123b Communications Software. Overview for today. Names and Addresses. Goals for a naming system. Internet Hostnames

DISTRIBUTED SYSTEMS [COMP9243] Lecture 9a: Naming WHAT IS NAMING? Name: Entity: Slide 3. Slide 1. Address: Identifier:

ICS 351: Today's plan. DNS WiFi

BU-2 How Protocols Work 16 June 2009

Peer-to-Peer Networks and the DNS

A Root DNS Server. Akira Kato. Brief Overview of M-Root. WIDE Project

Lecture 10: Protocol Design

Protocol Classification

System Up and Running. We are now going to shut down the system. Load Average: How Busy the System Is. System Halt (1)

Internet Engineering Task Force (IETF) Request for Comments: 7706 Category: Informational ISSN: November 2015

DNS Basics BUPT/QMUL

Introduction to Network. Topics

Application Layer: OSI and TCP/IP Models

Lecture 05: Application Layer (Part 02) Domain Name System. Dr. Anis Koubaa

CSCE 463/612 Networks and Distributed Processing Spring 2018

Domain Name Service. in-addr sfu

0 0& Basic Background. Now let s get into how things really work!

Internet Technology. 06. Exam 1 Review Paul Krzyzanowski. Rutgers University. Spring 2016

In This Issue. From The Editor

CSE561 Naming and DNS. David Wetherall

A DNS Tutorial

Network+ Guide to Networks, Seventh Edition Chapter 2, Solutions

DISTRIBUTED SYSTEMS Principles and Paradigms Second Edition ANDREW S. TANENBAUM MAARTEN VAN STEEN. Chapter 5 Naming

04 Identifiers. UUID URI Format Characteristics. Coulouris, Ch 9 rfc3986 Ahmed, 2005 Subharthi, 2009

Configuring DNS. Finding Feature Information. Information About DNS Clients. DNS Client Overview

CSE 124 January 18, Winter 2017, UCSD Prof. George Porter

Final Exam Computer Networks Fall 2015 Prof. Cheng-Fu Chou

Chapter 2 Application Layer. Lecture 5 DNS. Computer Networking: A Top Down Approach. 6 th edition Jim Kurose, Keith Ross Addison-Wesley March 2012

Computer Network laboratory (2015) Pattern TE Computer 1 (5)

IPV6 ON THE INTERNET

Computer Networks.. By Nidhi Jindal

04 Identifiers UUID. Coulouris, Ch 9 URI. rfc3986 Format. Ahmed, 2005 Characteristics. Subharthi, 2009

CE Advanced Network Security

DEPLOYMENT GUIDE Version 1.1. DNS Traffic Management using the BIG-IP Local Traffic Manager

POWERLINK QUICK START MANUAL V2.8

Lecture 20: Automated Fault Management

Automated Fault Management. Lecture 20: Prof. Shervin Shirmohammadi SITE, University of Ottawa. Prof. Shervin Shirmohammadi CEG

Configuring DNS. Finding Feature Information

Lecture 8: Flow Analysis

More on DNS and DNSSEC

CS 43: Computer Networks. 10: Naming and DNS September 24, 2018

APPLICATION LAYER APPLICATION LAYER : DNS, HTTP, , SMTP, Telnet, FTP, Security-PGP-SSH.

6to4 reverse domain delegation ip6.arpa

CS155b: E-Commerce. Lecture 3: Jan 16, How Does the Internet Work? Acknowledgements: S. Bradner and R. Wang

Page 1. CS162 Operating Systems and Systems Programming Lecture 22. Networking III. Automatic Repeat Request

Internet Technology 3/2/2016

Chapter 4. Internet Applications

Domain Name System (DNS)

DNS & Iodine. Christian Grothoff.

CSc 450/550 Computer Networks Domain Name System

FINAL EXAM REVIEW PLEASE NOTE THE MATERIAL FROM LECTURE #16 at the end. Exam 1 Review Material

CS 457 Lecture 11 More IP Networking. Fall 2011

Networking Basics. EC512 Spring /15/2015 EC512 - Prof. Thomas Skinner 1

Computer Networks. Domain Name System. Jianping Pan Spring /25/17 CSC361 1

Introduction to the Domain Name System

Lecture 18: Network Management

Binary Octet to Decimal Format Conversion

Computer Science 425 Distributed Systems CS 425 / ECE 428. Fall 2013

Security Impact of DNS Delegation Structure and Configuration Problems

Today: Naming. Example: File Names

IT 341: Introduction to System

To use DNS, you must have a DNS name server on your network.

ROOT SERVERS MANAGEMENT AND SECURITY

Transcription:

Lecture 4: Basic Internet Operations Prof. Shervin Shirmohammadi SITE, University of Ottawa Prof. Shervin Shirmohammadi CEG 4395 4-1

LAN View A LAN 2 B Hub 2 Gateway to Internet Hub 1 Z (Gateway) LAN 1 LAN N Prof. Shervin Shirmohammadi CEG 4395 4-2

outbound packet Internet View A LAN 2 B Hub 2 Gateway to Internet Z Hub 1 (Gateway) LAN 1 LAN N deliver packet A LAN 2 B Hub 2 Gateway to Internet Internet Hub 1 Z (Gateway) LAN 1 LAN N How to find the IP address of the destination? Prof. Shervin Shirmohammadi CEG 4395 4-3

DNS Domain Name System (DNS) is a client-server application that identifies each host on the Internet with a unique user-friendly name; e.g., cbc.ca instead of 159.33.3.85 A name space that maps each address to a unique name can be organized in two ways: flat or hierarchical. Flat: each name consists of a sequence of characters without any further structure; e.g., ComputerNumber376UniversityofOttawaCanada. Hierarchical: each name is made of several parts, such as organization, department, country, and computer name; e.g., site0.site.uottawa.ca Prof. Shervin Shirmohammadi CEG 4395 4-4

Domain Name Space The namespace is partitioned at the top level, and authority for names in subdivision is passed to designated agents. Each label is restricted to 63 characters. Prof. Shervin Shirmohammadi CEG 4395 4-5

Top Level Internet Domains The IANA (Internet Assigned Numbers Authority) handles domain naming. www.iana.org Prof. Shervin Shirmohammadi CEG 4395 4-6

Domain Name and Label Label: each section of a name Prof. Shervin Shirmohammadi CEG 4395 4-7

Hierarchy of Name Servers There is a server responsible for a given top-domain. Each server must know the address of all its lower-level servers for its sub-domains. What is the problem with this approach? Prof. Shervin Shirmohammadi CEG 4395 4-8

A Realistic Hierarchy The tree is more flat than the theoretical one on the previous slide. Hence, fewer servers must be contacted to find a given host. Prof. Shervin Shirmohammadi CEG 4395 4-9

13 Root Name Servers a.root-servers.net 198.41.0.4 b.root-servers.net 128.9.0.107 c.root-servers.net 192.33.4.12 d.root-servers.net 128.8.10.90 e.root-servers.net 192.203.230.10 f.root-servers.net 192.5.5.241 g.root-servers.net 192.112.36.4 h.root-servers.net 128.63.2.53 i.root-servers.net 192.36.148.17 j.root-servers.net 198.41.0.10 k.root-servers.net 193.0.14.129 l.root-servers.net 198.32.64.12 m.root-servers.net 202.12.27.33 Prof. Shervin Shirmohammadi CEG 4395 4-10

Primary and Secondary Servers Primary: creates, maintains, and updates information about its zone. Secondary: gets its information from a primary server; does not create, maintain, or update information about its zone. Both servers have authority over their zone. The idea here is to have a backup server in case of failure. Prof. Shervin Shirmohammadi CEG 4395 4-11

Internet Domain Categories Servers are divided into 3 different categories. Prof. Shervin Shirmohammadi CEG 4395 4-12

Generic Domain Prof. Shervin Shirmohammadi CEG 4395 4-13

Country Domain Prof. Shervin Shirmohammadi CEG 4395 4-14

Inverse Domain IP address 132.34.45.121 is represented as 121.45.34.132.in-addr.arpa. What is the benefit of such a lookup service? Prof. Shervin Shirmohammadi CEG 4395 4-15

DNS Software Name server: A server program that supplies name-to-address translation, mapping from domain names to IP addresses (and vice versa). Name resolver: client program that uses one or more name servers when translating a name. Resolver accesses the closest DNS, asking for a mapping. Recursive lookup Iterative lookup Prof. Shervin Shirmohammadi CEG 4395 4-16

Recursive Resolution E.g.: Host 1: client.fhda.edu Host 2: www.mcgraw.com Prof. Shervin Shirmohammadi CEG 4395 4-17

Iterative Resolution Prof. Shervin Shirmohammadi CEG 4395 4-18

DNS Message Format Identification: a unique number for client to match response to query Question: the lookup request Answer: the lookup answer Authority: the closest DNS suitable for this request. Clients are encouraged to cache this information for further requests. Prof. Shervin Shirmohammadi CEG 4395 4-19

Parameter Field Prof. Shervin Shirmohammadi CEG 4395 4-20

DNS Communication Protocol Client-server architecture, with server usually listening on UDP port 53, and sometimes TCP port 53. Why is UDP preferred to TCP? Client creates an ID and sends a message, with the format shown in slide 7-19, to the primary DNS server. Server responds, using the ID provided. Server communicates with higher-level servers in a similar way, if required. Duplicate responses are dropped. Security concerns? Prof. Shervin Shirmohammadi CEG 4395 4-21

Example C:\>nslookup www.cbc.ca Server: infofan.site.uottawa.ca Address: 137.122.89.39 Non-authoritative answer: Name: a1849.gc.akamai.net Addresses: 208.38.45.183, 208.38.45.191 Aliases: www.cbc.ca, www.cbc.ca.edgesuite.net Prof. Shervin Shirmohammadi CEG 4395 4-22

Network Address Translation (NAT) Although it is against the Internet architecture, we don t really need unique IP addresses (unique to the Internet) for nodes on our private network, as long as we know how to route packets to the right destinations. A B Z LAN 2 Hub 1 (Gateway) LAN 1 LAN N Hub 2 Gateway to Internet As long as Hub 2 acts as a proxy and knows how to get an incoming packet to A, B,, and Z, it doesn t matter if A, b, and Z s IP addresses are not unique compared to the rest of the Internet. Prof. Shervin Shirmohammadi CEG 4395 4-23

192.168.0.1 NAT Operation 192.168.0.2 S-port=8777 S-IP=192.168.0.2 S-port=63211S-IP=137.122.20.1 Router NAT 137.122.20.1 D-port=8777 D-IP=192.168.02 D-port=63211D-IP=137.122.20.1 Internet 192.168.0.10 NAT port = 63210 port=5113 S-IP=192.168.0.10 NAT port = 63211 port=8777 S-IP=192.168.0.2 NAT port = 63212 port=6522 S-IP=192.168.0.1 Prof. Shervin Shirmohammadi CEG 4395 4-24

WWW World Wide Web uses a client-server model. Prof. Shervin Shirmohammadi CEG 4395 4-25