Development of the Domain Name System
|
|
- Jocelin O’Brien’
- 5 years ago
- Views:
Transcription
1 Development of the Domain Name System Paul V. Mockapetris, Keven J. Dunlap Presenter: Gigis Petros ACM SIGCOMM 88
2 Introduction What was before DNS? Before DNS we were using HOSTS.TXT system for publishing the mapping between host names and addresses The HOSTS.TXT was headed for problems
3 What is HOSTS.TXT? HOSTS.TXT is a simple text file, which is centrally maintained on a host at the SRI Network Information Center (SRI-NIC) Distributed to all hosts in the Internet via file transfers
4 Problems with HOSTS.TXT The file size and cost of distribution were becoming too large Centralized control of updating the file was against the trend toward more distributed management of the Internet. Increasement of hosts, organizations and file transfers was much larger than linear increase
5 Introduction Organizations were being forced into management of local network addresses, gateways, etc.. Need to partition the database and allow local control of name and address spaces A distributed name system was needed The existing distributed name systems were not suitable for the DARPA Internet
6 And Eureka! Domain Name System (DNS)
7 Initial Design of DNS Initial designed started in 1983 Base design assumptions for the DNS: 1. Provide at least all the same information as HOSTS.TXT 2. Allow database to be maintained in a distributed manner 3. No obvious size limits for names, types, etc 4. Interoperate across the DARPA Internet and other non TCP/IP projects 5. Provide tolerable performance
8 Initial Design of DNS Independence of Network topology Capable of encapsulating other name spaces OS independent Hierarchical design Distribution & size requirements Main Goal: Lean but Distributed Lean more implementation & quick availability Lead to removal of dynamic update of db with related atomicity, voting and backup considerations General design = more applications, increase functionality and increase number of enviroment under which DNS is deployed
9 Architecture of DNS Two major active components: Name Servers: Repositories of information Answer queries using whatever information they possess Resolvers: Interface to client programs Algorithms to contact name servers
10 The Name Space 1/2 The DNS internal name space is a variable-depth tree Each node has an associated case-insensitive label Labels are variable length 8-bit octets (Max = 63 octets) Name are restricted to 256 octets Tree structure allows overloading of names across different subtrees The domain name of a node is the concatenation of all labels on the path from the node to the root of the tree The zero length label is reserved for the root Top level domains are for country or broad organizational codes (uk, com, edu, etc)
11 The Name Space 2/2
12 Data attached to names Data for each name is organized as a set of resource records (RRs) Multiple values of the same type are represented as separate RRs Limited size datagram (UDP) - dont have to deal with breaking up maximum sized packet Each RR carries a well-known type and class field, followed by applications data Types represent abstract resources or functions (example: Host Addresses and mailboxes) Class field specifies the protocol family or instance (Internet, DARPA, CHAOS, ISO, etc)
13 Data Distribution Two major mechanisms for transferring data Zones Contiguous portion of the domain name space for which administrative responsibility has been delegated to an organization Caching Mechanism whereby data acquired in response to a client s request can be locally stored against future requests Both mechanisms invisible to the user who should see a single database
14 Zones Contiguous description of tree space and pointer information for other relevant contiguous zones Could be an intire subtree or just a node Distribute several copies to several servers to handle requests by clients Creation Begins with request to parent zone to delegate a subnode Grow as a tree within the node Parent records in RRs that zone records for particular node have a zone division and point to new zone holder Parent should not be involved henceforth
15 Zones Organization maintains zones and distributes zones appropriately Master file distributed to all users manually or DNS based algorithm - zone refresh Serial number based Zone transfer requires TCP Single name server can handle multiple zones (master/slave) Geographical distribution of data Data retrieved from zone = authoritative
16 Zones
17 Zones
18 Caching DNS resolvers programs responsible for caching A TTL field (in sec) is attached to each RR A low TTL is desirable because it minimizes inconsistency A high TTL minimizes traffic and allows caching to mask periods of server unavailability Recommended TTL value for host names is 2 days
19 Current Implementation Status
20 Current Implementation Status In 1987 HOSTS.TXT was still used by older hosts, but DNS became the recommended mechanism 5,500 host names were in HOSTS.TXT Over 20,000 host names available via DNS Domain space was petitioned into roughly 30 top level domains The delegation of subdomains by the SRI-NIC has grown steadily In 1987 roughly 300 domains were delegated In 1988 roughly 650 domains were delegated
21 Implementation Status 1988 Two good examples of contemporary DNS use: Root servers Berkley subdomain
22 Root Servers in 1988 Root domain is supported by 7 redundant name servers Typical traffic rate a query/sec Four types of queries: All information (25-40%) Address mappings (30-40%) Address to host mappings (10-15%) MX less than 10%
23 Berkeley in 1988 Due to growth in the campus network they developed BIND (Berkeley Internet Name Domain) server First organization on the DARPA Internet to bring up machines with all their network applications solely dependent on DNS Difficult to adopt it from users
24 Surprises Operation of the DNS has revealed several issues that came as surprises to the developers Refinement of semantics Performance Negative caching
25 Surprises Refinement of Semantics The DNS is to act as a repository for information and the initial assumption was that the form and content of the information in DNS was well-understood. (order, metric for multiple addresses to host) Performance Performance of the underlying network was much worse than the original design expected The reasons for the longer delays were: 1. Growth in the number of networks 2. Growth in load 3. The addition of many lower speed links At the root servers clients typically see response times of 500 ms to 5 secs. At delegated domain 3-10 secs and some times secs
26 Negative Caching DNS provides two negative responses to queries 1. The name in query does not exist 2. The name in query exists but the requested data does not (query maybe for a mailbox) Initial monitoring of root server showed a very high percentage 20-60% of these responses Expected negatives responses to go down, but they stayed in the 10-50% range Decided they needed caching for negative results
27 Successes Variable depth hierarchy Additional section processing Organizational structuring of names Datagram access Caching Mail address cooperation
28 Variable depth hierarchy Successes Huge number of workstations lead to organizations better organizing themselves instead of single flat file Organizations are of different sizes depth should be of different levels Additional section processing Add any additional information as long as the data fits in a single datagram Can answer a request before it was asked Cuts query traffic in half
29 Successes Organizational structuring of names Names are independent of network topology, etc. was popular Datagram access Datagram used to access name servers was successful because of the bad performance of the DARPA Internet Drawback: need to develop and refine retransmission strategies
30 Successes Caching Caching discipline of the DNS works well and was essential to the success of the system But caching make it less reliable or useful Mail address cooperation Different Internet communities agreed to use organizationally structured domain names for mail addressing and routing
31 Shortcomings Type and class growth Easy upgrading of applications Distribution of control vs distribution of expertise or responsibility
32 Shortcomings Type and class growth Difficult to make new definitions Need to clearly design and publish their semantics Create applications to use them Easy upgrading of applications Not easy to convert network applications to use the DNS DNS resolver must be part of the OS Distribution of control vs distribution of expertise or responsibility Organizations should have been required to have redundant servers with real data before they were given a domain Documentation should always be well-written and simple
33 Was the DNS a good idea? Modifications to the HOSTS.TXT scheme could have postponed the need for a new system but need to distribute functionality was crucial and with the new functionality and the opportunities for future services it was a good idea!
34 Conclusion Things they wished they had known earlier: Caching works well, but caching for negative responses is needed It is more difficult to remove a function than to add new one Optimizations are not considered if the system performs at the expected level Allowing variations in the provided service causes problems
35
36 Backup
ECE 650 Systems Programming & Engineering. Spring 2018
ECE 650 Systems Programming & Engineering Spring 2018 Dynamic Host Configuration Protocol (DHCP) and Domain Name System (DNS) Tyler Bletsch Duke University Slides are adapted from Brian Rogers (Duke) Dynamic
More informationDNS and Modern Network Services. Amin Vahdat CSE 123b April 27, 2006
DNS and Modern Network Services Amin Vahdat CSE 123b April 27, 2006 Midterm: May 9 Annoucements Second assignment due May 15 Domain Name System Motivation 1982: single hosts.txt file stored and distributed
More informationA DNS Tutorial
http://ntrg.cs.tcd.ie/undergrad/4ba2/multicast/ Copyright Table of Contents What is a DNS?... 3 Why do we need a DNS?... 3 Why do computers prefer addresses based on numbers?... 3 What is a Domain Name,
More informationCSE 124 January 18, Winter 2017, UCSD Prof. George Porter
CSE 124 January 18, 2017 Winter 2017, UCSD Prof. George Porter Comic by A&K of chaoslife.findchaos.com Lesson of the day 1: Always backup your computer Lesson of the day 2: That backup needs to be automatic!
More informationCSE 124 January 27, Winter 2017, UCSD Prof. George Porter
CSE 124 January 27, 2017 Winter 2017, UCSD Prof. George Porter Announcements Today s plan: Finish up DNS/naming Bit more detail on threading and synchronization Open discussion about Project 1 Part 1:
More informationDomain Name System.
Domain Name System http://xkcd.com/302/ CSCI 466: Networks Keith Vertanen Fall 2011 Overview Final project + presentation Some TCP and UDP experiments Domain Name System (DNS) Hierarchical name space Maps
More information0 0& Basic Background. Now let s get into how things really work!
+,&&-# Department of Electrical Engineering and Computer Sciences University of California Berkeley Basic Background General Overview of different kinds of networks General Design Principles Architecture
More informationDNS/DNSSEC Workshop. In Collaboration with APNIC and HKIRC Hong Kong. Champika Wijayatunga Regional Security Engagement Manager Asia Pacific
DNS/DNSSEC Workshop In Collaboration with APNIC and HKIRC Hong Kong Champika Wijayatunga Regional Security Engagement Manager Asia Pacific 22-24 January 2018 1 Agenda 1 2 3 Introduction to DNS DNS Features
More informationNetworking Applications
Networking Dr. Ayman A. Abdel-Hamid College of Computing and Information Technology Arab Academy for Science & Technology and Maritime Transport 1 Outline Introduction Name Space concepts Domain Name Space
More informationNaming. To do. q What s in a name q Flat naming q Structured naming q Attribute-based naming q Next: Content distribution networks
Naming To do q What s in a name q Flat naming q Structured naming q Attribute-based naming q Next: Content distribution networks What's in a name? That which we call a rose By any other name would smell
More informationProtocol Classification
DNS and DHCP TCP/IP Suite Suite of protocols (not just TCP and IP) Main protocols TCP and UDP at the Transport Layer, and IP at the Network Layer Other protocols ICMP, ARP, Telnet, Ftp, HTTP, SMTP, SNMP
More informationS Computer Networks - Spring What and why? Structure of DNS Management of Domain Names Name Service in Practice
Outline What and why? Structure of DNS Management of Domain Names Name Service in Practice 188lecture12.ppt Pirkko Kuusela, Markus Peuhkuri, Jouni Karvo 1 2 Need Network addresses are numbers Addresses
More informationThe Domain Name System
The Domain Name System History of DNS Before DNS ARPAnet HOSTS.txt contains all the hosts information Maintained by SRI s Network Information Center In SRI-NIC host Problems: Not scalable! Traffic and
More informationCSE 124 January 12, Winter 2016, UCSD Prof. George Porter
CSE 124 January 12, 2016 Winter 2016, UCSD Prof. George Porter Announcements HW 2 due on Thursday Project 1 has been posted Today s plan: Finish discussing server sockets DNS: the Domain Name System API
More informationChapter 19. Domain Name System (DNS)
Chapter 19 Domain Name System (DNS) TCP/IP Protocol Suite 1 Copyright The McGraw-Hill Companies, Inc. Permission required for reproduction or display. OBJECTIVES: To describe the purpose of DNS. To define
More informationClient Server Concepts, DNS, DHCP
Client Server Concepts, DNS, DHCP Prof. I. Sengupta / Dr. S.K. Ghosh School of Information Technology Indian Institute of Technology, Kharagpur 1 Client-Server Model 2 Client-server Model Standard model
More informationObjectives. Upon completion you will be able to:
Domain Name System: DNS Objectives Upon completion you will be able to: Understand how the DNS is organized Know the domains in the DNS Know how a name or address is resolved Be familiar with the query
More informationAPNIC elearning: DNS Concepts
APNIC elearning: DNS Concepts 27 MAY 2015 11:00 AM AEST Brisbane (UTC+10) Issue Date: Revision: Introduction Presenter Sheryl Hermoso Training Officer sheryl@apnic.net Specialties: Network Security IPv6
More informationThe State and Challenges of the DNSSEC Deployment. Eric Osterweil Michael Ryan Dan Massey Lixia Zhang
The State and Challenges of the DNSSEC Deployment Eric Osterweil Michael Ryan Dan Massey Lixia Zhang 1 Monitoring Shows What s Working and What needs Work DNS operations must already deal with widespread
More informationCSE561 Naming and DNS. David Wetherall
CSE561 Naming and DNS David Wetherall djw@cs.washington.edu Naming and DNS Focus: How do we resolve names to addresses Names and addresses Application DNS as a system design Transport Network Link Physical
More informationCHAPTER 22 DISTRIBUTED APPLICATIONS ANSWERS TO QUESTIONS ANSWERS TO PROBLEMS
CHAPTER 22 DISTRIBUTED APPLICATIONS ANSWERS TO QUESTIONS 22.1 RFC 821 defines SMTP which is the protocol for exchanging email messages. RFC 822 describes the format of those messages. 22.2 The Simple Mail
More informationCommunications Software. CSE 123b. CSE 123b. Spring Lecture 11: Domain Name System (DNS) Stefan Savage. Some pictures courtesy David Wetherall
CSE 123b CSE 123b Communications Software Spring 2003 Lecture 11: Domain Name System (DNS) Stefan Savage Some pictures courtesy David Wetherall & Srini Seshan Where we ve been & where we re going Low-level
More informationCSE 123b Communications Software. Overview for today. Names and Addresses. Goals for a naming system. Internet Hostnames
CSE 123b Communications Software Spring 2003 Lecture 11: Domain Name System (DNS) Stefan Savage Where we ve been & where we re going Low-level networking (so far) Internetworking architecture Packet Forwarding
More informationDNS Basics BUPT/QMUL
DNS Basics BUPT/QMUL 2018-04-16 Related Information Basic function of DNS Host entry structure in Unix Two system calls for DNS database retrieving gethostbyname () gethostbyaddr () 2 Agenda Brief introduction
More informationUNIT III 1. Enumerate the properties of storage system? Sharing Persistent Distributed Consistency Example cache/replicas maintenance Main memory No No No 1 RAM File system n No Yes No 1 UNIX file system
More informationEECS 122: Introduction to Computer Networks DNS and WWW. Internet Names & Addresses
EECS 122: Introduction to Computer Networks DNS and WWW Computer Science Division Department of Electrical Engineering and Computer Sciences University of California, Berkeley Berkeley, CA 94720-1776 Internet
More informationLinux System Administration
IP Addressing Subnetting Objective At the conclusion of this module, the student will be able to: Describe how packets are routed from one network to another Describe the parts and classes of IPv4 address
More informationDNS Concepts. Acknowledgements July 2005, Thimphu, Bhutan. In conjunction with SANOG VI. Bill Manning Ed Lewis Joe Abley Olaf M.
16-20 July 2005, Thimphu, Bhutan In conjunction with SANOG VI DNS Concepts Acknowledgements Bill Manning Ed Lewis Joe Abley Olaf M. Kolkman NeuStar 1 Purpose of naming Addresses are used to locate objects
More informationRe-engineering the DNS One Resolver at a Time. Paul Wilson Director General APNIC channeling Geoff Huston Chief Scientist
Re-engineering the DNS One Resolver at a Time Paul Wilson Director General APNIC channeling Geoff Huston Chief Scientist 1 In this presentation I ll talk about the DNS, and the root server infrastructure
More informationOverview General network terminology. Chapter 9.1: DNS
Overview General network terminology Chapter 9.1: DNS Jan-29-04 4/598N: Computer Networks 1 Connection mechanisms Connectionless or packet switching Each packet carries with it the source and destination
More informationIntroduction to the Domain Name System
The Domain Name System (DNS) handles the growing number of Internet users. DNS translates names, such as www.cisco.com, into IP addresses, such as 192.168.40.0 (or the more extended IPv6 addresses), so
More informationNetwork Security Part 3 Domain Name System
Network Security Part 3 Domain Name System Domain Name System The$domain$name$system$(DNS)$is$an$applica6on7layer$ protocol$$for$mapping$domain$names$to$ip$addresses$ DNS www.example.com 208.77.188.166
More informationRequest for Comments: 882 November
Network Working Group Request for Comments: 882 P. Mockapetris ISI November 1983 INTRODUCTION DOMAIN NAMES - CONCEPTS and FACILITIES +-----------------------------------------------------+ This RFC introduces
More informationDNS and HTTP. A High-Level Overview of how the Internet works
DNS and HTTP A High-Level Overview of how the Internet works Adam Portier Fall 2017 How do I Google? Smaller problems you need to solve 1. Where is Google? 2. How do I access the Google webpage? 3. How
More informationA Self-Configuring and Self-Administering Name System
A Self-Configuring and Self-Administering Name System by Michael L. Feng Submitted to the Department of Electrical Engineering and Computer Science in Partial Fulfillment of the Requirements for the Degree
More informationApplication Layer Protocols
Application Layer Protocols Dr. Ihsan Ullah Department of Computer Science & IT University of Balochistan, Quetta Pakistan Email: ihsan.ullah.cs@gmail.com These slides are adapted from the slides accompanying
More informationUNIT III. cache/replicas maintenance Main memory No No No 1 RAM File system n No Yes No 1 UNIX file system Distributed file
UNIT III 1. Enumerate the properties of storage system? Sharing Persistent Distributed Consistency Example cache/replicas maintenance Main memory No No No 1 RAM File system n No Yes No 1 UNIX file system
More informationpage 1 Plain Old DNS WACREN, DNS/DNSSEC Regional Workshop Ouagadougou, October 2016
page 1 Plain Old DNS WACREN, DNS/DNSSEC Regional Workshop Ouagadougou, 10-14 October 2016 page 2 IP: Identifiers on the Internet The fundamental identifier on the internet is an IP address. Each host connected
More informationComputer Networks.. By Nidhi Jindal
Computer Networks APPLICATION LAYER: DNS. By Nidhi Jindal INTRODUCTION A user of an e mail program may know the e mail address of the recipient; however, the IP protocol needs the IP address. The DOMAIN
More informationNetwork Working Group. November 1987
Network Working Group Request For Comments: 1033 M. Lottor SRI International November 1987 DOMAIN ADMINISTRATORS OPERATIONS GUIDE STATUS OF THIS MEMO This RFC provides guidelines for domain administrators
More informationDNS. Introduction To. everything you never wanted to know about IP directory services
Introduction To DNS everything you never wanted to know about IP directory services Linux Users Victoria, April 3 rd 2007 what is the domain name system anyway? it's like a phone book...kinda DNS is (1)
More informationThe Interconnection Structure of. The Internet. EECC694 - Shaaban
The Internet Evolved from the ARPANET (the Advanced Research Projects Agency Network), a project funded by The U.S. Department of Defense (DOD) in 1969. ARPANET's purpose was to provide the U.S. Defense
More informationOutline Applications. Central Server Hierarchical Peer-to-peer. 31-Jan-02 Ubiquitous Computing 1
Outline Applications Central Server Hierarchical Peer-to-peer 31-Jan-02 Ubiquitous Computing 1 Networked distributed system architectures Central Server based Web servers Hierarchical Services Domain Name
More informationThe Domain Name System
The Domain Name System History of DNS Before DNS ARPAnet HOSTS.txt contains all the hosts information Maintained by SRI s Network Information Center In SRI-NIC host Problems: Not scalable! Traffic and
More informationThis time. Digging into. Networking. Protocols. Naming DNS & DHCP
This time Digging into Networking Protocols Naming DNS & DHCP Naming IP addresses allow global connectivity But they re pretty useless for humans! Can t be expected to pick their own IP address Can t be
More informationElectrical Engineering Department EE 400, Experiment # 4 IP Addressing and Subnetting
Electrical Engineering Department EE 400, Experiment # 4 IP Addressing and Subnetting Objectives: After this experiment, the students should be able to configure for networking, assign IP address, and
More informationRequest for Comments: Category: Informational October 1994
Network Working Group Request for Comments: 1706 Obsoletes: 1637, 1348 Category: Informational B. Manning ISI R. Colella NIST October 1994 DNS NSAP Resource Records Status of this Memo This memo provides
More informationGuide to Networking Essentials, 6 th Edition. Chapter 5: Network Protocols
Guide to Networking Essentials, 6 th Edition Chapter 5: Network Protocols Objectives Describe the purpose of a network protocol, the layers in the TCP/IP architecture, and the protocols in each TCP/IP
More information04 Identifiers. UUID URI Format Characteristics. Coulouris, Ch 9 rfc3986 Ahmed, 2005 Subharthi, 2009
04 Identifiers UUID URI Format Characteristics Coulouris, Ch 9 rfc3986 Ahmed, 2005 Subharthi, 2009 Resource identification All resources should have a name Resource without Identifier Can not be shared
More informationUDP. Networked Systems (H) Lecture 15
UDP Networked Systems (H) Lecture 15 This work is licensed under the Creative Commons Attribution-NoDerivatives 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nd/4.0/
More informationGoal of this session
DNS refresher Overview Goal of this session What is DNS? How is DNS built and how does it work? How does a query work? Record types Caching and Authoritative Delegation: domains vs zones Finding the error:
More informationChapter 7. Local Area Network Communications Protocols
Chapter 7 Local Area Network Communications Protocols The Network Layer The third layer of the OSI Model is the network layer. The network layer is concerned with providing a means for hosts to communicate
More informationCS519: Computer Networks. Lecture 6: Apr 5, 2004 Naming and DNS
: Computer Networks Lecture 6: Apr 5, 2004 Naming and DNS Any problem in computer science can be solved with another layer of indirection David Wheeler Naming is a layer of indirection What problems does
More informationNetworking Basics. EC512 Spring /15/2015 EC512 - Prof. Thomas Skinner 1
Networking Basics EC512 Spring 2015 2/15/2015 EC512 - Prof. Thomas Skinner 1 Protocols Protocols are required in order to allow information to be extracted from the stream of bits flowing from one point
More informationDistributed Operating Systems
Distributed Operating Systems Name no more precise Interesting/advanced Topics in Operating Systems scalability systems security modeling Some overlap with Distributed Systems (Prof Schill) In some cases
More informationHigher layer protocols
ETSF05/ETSF10 Internet Protocols Higher layer protocols DHCP DNS Real time applications RTP The hen or the egg? DHCP IP addr. IP DNS TCP UDP ETSF05/ETSF10 - Internet Protocols 2 What to configure IP address
More informationINTERNET ARCHITECTURE & PROTOCOLS
INTERNET ARCHITECTURE & PROTOCOLS Set # 01 Delivered By: Engr Tahir Niazi What is Internet? Basically it is called Network of networks Nuts and Bolts (Pieces of internet) Services description (applications)
More informationThe Design and Implementation of a Next Generation Name Service for the Internet (CoDoNS) Presented By: Kamalakar Kambhatla
The Design and Implementation of a Next Generation Name Service for the Internet (CoDoNS) Venugopalan Ramasubramanian Emin Gün Sirer Presented By: Kamalakar Kambhatla * Slides adapted from the paper -
More informationConfiguring DNS. Finding Feature Information
The Domain Name System (DNS) is a distributed database in which you can map hostnames to IP addresses through the DNS protocol from a DNS server. Each unique IP address can have an associated hostname.
More informationNetwork+ Guide to Networks 5 th Edition. Chapter 10 In-Depth TCP/IP Networking
Network+ Guide to Networks 5 th Edition Chapter 10 In-Depth TCP/IP Networking Objectives Understand methods of network design unique to TCP/IP networks, including subnetting, CIDR, and address translation
More informationTop-Down Network Design
Top-Down Network Design Chapter Six Designing Models for Addressing and Naming Original slides copyright by Cisco Press & Priscilla Oppenheimer General Guidelines for Addressing and Naming Use a structured
More informationDomain Name System (DNS) DNS Fundamentals. Computers use IP addresses. Why do we need names? hosts.txt does not scale. The old solution: HOSTS.
Domain Name System (DNS) Computers use IP addresses. Why do we need names? Names are easier for people to remember DNS Fundamentals Computers may be moved between networks, in which case their IP address
More information1/18/13. Network+ Guide to Networks 5 th Edition. Objectives. Chapter 10 In-Depth TCP/IP Networking
Network+ Guide to Networks 5 th Edition Chapter 10 In-Depth TCP/IP Networking Objectives Understand methods of network design unique to TCP/IP networks, including subnetting, CIDR, and address translation
More informationBIG-IP DNS: Implementations. Version 12.0
BIG-IP DNS: Implementations Version 12.0 Table of Contents Table of Contents Legal Notices...9 Legal notices...9 Integrating BIG-IP DNS Into a Network with BIG-IP LTM Systems...11 Overview: Integrating
More informationIP ADDRESSES, NAMING, AND DNS
IP ADDRESSES, NAMING, AND DNS George Porter Apr 9, 2018 ATTRIBUTION These slides are released under an Attribution-NonCommercial-ShareAlike 3.0 Unported (CC BY-NC-SA 3.0) Creative Commons license These
More informationConfiguring DNS. Finding Feature Information. Prerequisites for Configuring DNS
The Domain Name System (DNS) is a distributed database in which you can map host names to IP addresses through the DNS protocol from a DNS server. Each unique IP address can have an associated host name.
More informationChapter 6. The Protocol TCP/IP. Introduction to Protocols
Chapter 6 The Protocol TCP/IP 1 Introduction to Protocols A protocol is a set of rules that governs the communications between computers on a network. These rules include guidelines that regulate the following
More informationDNS & Iodine. Christian Grothoff.
DNS & Iodine christian@grothoff.org http://grothoff.org/christian/ The Domain Name System is the Achilles heel of the Web. Tim Berners-Lee 1 DNS: Domain Name System Unique Distributed Database Application-layer
More informationNetworking and Internetworking 1
Networking and Internetworking 1 Today l Networks and distributed systems l Internet architecture xkcd Networking issues for distributed systems Early networks were designed to meet relatively simple requirements
More information04 Identifiers UUID. Coulouris, Ch 9 URI. rfc3986 Format. Ahmed, 2005 Characteristics. Subharthi, 2009
04 Identifiers UUID Coulouris, Ch 9 URI rfc3986 Format Ahmed, 2005 Characteristics Subharthi, 2009 Resource identification All resources should have a name Resource without Identifier Can not be shared
More informationRequest for Comments: 1101 Updates: RFCs 1034, 1035 April 1989
Network Working Group P. Mockapetris Request for Comments: 1101 ISI Updates: RFCs 1034, 1035 April 1989 DNS Encoding of Network Names and Other Types 1. STATUS OF THIS MEMO This RFC proposes two extensions
More informationICS 351: Networking Protocols
ICS 351: Networking Protocols IP packet forwarding application layer: DNS, HTTP transport layer: TCP and UDP network layer: IP, ICMP, ARP data-link layer: Ethernet, WiFi 1 Networking concepts each protocol
More informationGuide to TCP/IP, Third Edition. Chapter 12: TCP/IP, NetBIOS, and WINS
Guide to TCP/IP, Third Edition Chapter 12: TCP/IP, NetBIOS, and WINS Objectives Discuss the history of NetBIOS Understand what NetBIOS is and its limitations Understand the role of NetBIOS in Windows 2000
More informationCS4/MSc Computer Networking. Lecture 3: The Application Layer
CS4/MSc Computer Networking Lecture 3: The Application Layer Computer Networking, Copyright University of Edinburgh 2005 Network Applications Examine a popular network application: Web Client-server architecture
More informationSmartDNS. Speed: Through load balancing, FatPipe's SmartDNS speeds up the delivery of inbound traffic.
SmartDNS FatPipe Networks is well known for its patented and patent pending technology that provides redundancy, high reliability, and aggregate speed of WAN connections. Its core innovation for intelligent
More informationDomain Name Service. DNS Overview. October 2009 Computer Networking 1
Domain Name Service DNS Overview October 2009 Computer Networking 1 Why DNS? Addresses are used to locate objects (contain routing information) Names are easier to remember and use than numbers DNS provides
More informationA Survey Paper on Grid Information Systems
B 534 DISTRIBUTED SYSTEMS A Survey Paper on Grid Information Systems Anand Hegde 800 North Smith Road Bloomington Indiana 47408 aghegde@indiana.edu ABSTRACT Grid computing combines computers from various
More informationSilberschatz and Galvin Chapter 15
Silberschatz and Galvin Chapter 15 Network Structures CPSC 410--Richard Furuta 3/30/99 1 Chapter Topics Background and motivation Network topologies Network types Communication issues Network design strategies
More informationSubject Introduction to Information Technology Paper code MSCIT-101
Q.1) Write a short note on following: (A) Buffer & register: MSC 1 st Sem Aug-2014 Subject Introduction to Information Technology Paper code MSCIT-101 Answer: To handle the execution of instructions and
More informationWe will discuss about three different static routing algorithms 1. Shortest Path Routing 2. Flooding 3. Flow Based Routing
In this lecture we will discuss about Routing algorithms Congestion algorithms Lecture 19 The routing algorithm is that part of the network layer software, which is responsible for deciding which output
More informationConfiguration of Authoritative Nameservice
Configuration of Authoritative Nameservice AfCHIX 2011 Blantyre, Malawi (based on slides from Brian Candler for NSRC) Recap DNS is a distributed database Resolver asks Cache for information Cache traverses
More informationApplication Layer -1- Network Tools
EITF25 Internet: Technology and Applications Application Layer -1- Network Tools 2013, Lecture 06 Kaan Bür, Stefan Höst Previously on EITF25 Transport Layer Addressing above IP Ports, sockets Process-to-process
More information12. Name & Address 최양희서울대학교컴퓨터공학부
12. Name & Address 최양희서울대학교컴퓨터공학부 How do you get IP address? Manual Configuration Stateful Address Configuration (i.e. from servers) BOOTP DHCPv4, DHCPv6 Stateless Autoconfiguration : IPv6 2009 Yanghee
More informationNetwork+ Guide to Networks 6 th Edition. Chapter 9 In-Depth TCP/IP Networking
Network+ Guide to Networks 6 th Edition Chapter 9 In-Depth TCP/IP Networking Objectives Describe methods of network design unique to TCP/IP networks, including subnetting, CIDR, and address translation
More informationCategory: Experimental June DNS NSAP Resource Records. Status of this Memo
Network Working Group Request for Comments: 1637 Obsoletes: 1348 Category: Experimental B. Manning Rice University R. Colella NIST June 1994 DNS NSAP Resource Records Status of this Memo This memo defines
More informationManual Configuration Stateful Address Configuration (i.e. from servers) Stateless Autoconfiguration : IPv6
Manual Configuration Stateful Address Configuration (i.e. from servers) BOOTP DHCPv4, DHCPv6 Stateless Auto : IPv6 최양희서울대학교컴퓨터공학부 2005 Yanghee Choi 2 RARP Hardware address ---> IP address requires direct
More informationVenugopal Ramasubramanian Emin Gün Sirer SIGCOMM 04
The Design and Implementation of a Next Generation Name Service for the Internet Venugopal Ramasubramanian Emin Gün Sirer SIGCOMM 04 Presenter: Saurabh Kadekodi Agenda DNS overview Current DNS Problems
More informationDEPLOYMENT GUIDE Version 1.1. DNS Traffic Management using the BIG-IP Local Traffic Manager
DEPLOYMENT GUIDE Version 1.1 DNS Traffic Management using the BIG-IP Local Traffic Manager Table of Contents Table of Contents Introducing DNS server traffic management with the BIG-IP LTM Prerequisites
More informationOverview. Last Lecture. This Lecture. Next Lecture. Scheduled tasks and log management. DNS and BIND Reference: DNS and BIND, 4 th Edition, O Reilly
Last Lecture Overview Scheduled tasks and log management This Lecture DNS and BIND Reference: DNS and BIND, 4 th Edition, O Reilly Next Lecture Address assignment (DHCP) TELE 301 Lecture 11: DNS 1 TELE
More informationDomain Name System (DNS) Session-1: Fundamentals. Joe Abley AfNOG Workshop, AIS 2017, Nairobi
Domain Name System (DNS) Session-1: Fundamentals Joe Abley AfNOG Workshop, AIS 2017, Nairobi Computers use IP addresses. Why do we need names? Names are easier for people to remember Computers may be moved
More informationPotential Name Syntax. Properties of Naming. Naming and system components. Naming and layering. Replicated storage, consistency
Naming and layering Naming and system components Replicated storage, consistency Caller Callee How to design interface between components? COS 518: Advanced Computer Systems Lecture 2 Mike Freedman Many
More informationLinux Network Administration
Linux Network Administration Objective Describe the organization of the namespace Define the top-level subdomains of the Describe the process of converting IP addresses into names Define the concept of
More informationAPPLICATION LAYER APPLICATION LAYER : DNS, HTTP, , SMTP, Telnet, FTP, Security-PGP-SSH.
APPLICATION LAYER : DNS, HTTP, E-mail, SMTP, Telnet, FTP, Security-PGP-SSH. To identify an entity, the Internet used the IP address, which uniquely identifies the connection of a host to the Internet.
More informationICS 351: Today's plan. DNS WiFi
ICS 351: Today's plan DNS WiFi Domain Name System Hierarchical system of names top-level domain names include.edu,.org,.com,.net, and many country top-level domains root is just "." so the fully qualified
More informationPerformance Evaluation of ENUM Directory Service Design
Performance Evaluation of ENUM Directory Service Design Hyewon K. Lee and Youngsong Mun School of Computing, Soongsil University, Seoul, Korea kerenlee@sunny.ssu.ac.kr, mun@computing.ssu.ac.kr Abstract.
More informationComputer Networking: Applications George Blankenship. Applications George Blankenship 1
CSCI 232 Computer Networking: Applications i George Blankenship Applications George Blankenship 1 TCP/IP Applications The user of TCP/IP transport (TCP/UDP) is an application, the top level lof the TCP/IP
More informationNetworking and Internetworking 1
Networking and Internetworking 1 To do q q Networks and distributed systems Internet architecture xkcd Internet history Early days ~1960 ARPA sponsored research on computer networking to enable remote
More informationNetworking Overview. CS Computer Security Profs. Vern Paxson & David Wagner
Networking Overview CS 161 - Computer Security Profs. Vern Paxson & David Wagner TAs: John Bethencourt, Erika Chin, Matthew Finifter, Cynthia Sturton, Joel Weinberger http://inst.eecs.berkeley.edu/~cs161/
More informationOpen Shortest Path First (OSPF)
CHAPTER 42 Open Shortest Path First (OSPF) Background Open Shortest Path First (OSPF) is a routing protocol developed for Internet Protocol (IP) networks by the interior gateway protocol (IGP) working
More informationCSE 5306 Distributed Systems
CSE 5306 Distributed Systems Naming Jia Rao http://ranger.uta.edu/~jrao/ 1 Naming Names play a critical role in all computer systems To access resources, uniquely identify entities, or refer to locations
More information