P. Mockapetris. RFC 1035 - Domain Names - Implementation and Specification, November 1987.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....logs) thresholds of 1180, 2660, 4140, which approximate responses taking one, two, and three UDP packets. We assume a 1480 byte datagram and deduct 300 bytes from the total size for HTTP headers and the DNS response itself. Although the DNS specification limits DNS responses to 512 bytes [10], this limitation was specified before MTU discovery has made 1480 byte packets ubiquitous and consequently led to the Proposed Standard (RFC 2671 [16] that specifies a method of increasing the DNS response size. A DEW capable server can just assume that, since it is receiving a DEW request, the ....

P. Mockapetris. RFC 1035: Domain names - implementation and specification, November 1987.

....of software and thus Figure 1: Working of recursive DNS servers both functions are sometimes preformed by the same host further fosters confusion. Even best of breed technical literature on DNS like [Alb01] uses imprecise language on this matter. To reduce confusion, naming convention based on [Moc87] Section 2.2, the standard defining DNS, should be used: Name Server The Purpose of name servers is the publishing of DNS data. They are part of the distributed DNS database and usually maintained by hosting providers or their associates. Persons not involved in the management of networks ....

....will be called recursive DNS servers in the rest of this paper. Further confusion arises from the fuzzy terminology relating to domain names. The terms host name , host , domain name , domain and site are often used as if they were interchangeable. Following definitions are based on [Moc87] and [Alb01] Domain Name A fully qualified domain name (FQDN) is a dotted string unambiguously pointing to an object in the global DNS database. For brevity it will be assumed in this paper that all domain names are FQDNs. Domain A domain is a subtree in the distributed DNS database. It can be ....

[Article contains additional citation context not shown here]

P. Mockapetris. RfC 1035: Domain Names - Implementation and Specification, 1987.

....II. OVERVIEW OF DNS In this section we provide a brief overview of DNS and introduce some terminology that we shall use throughout the paper. The principle task of the DNS is to provide a mapping from the human readable domain names to numerical IP addresses used to identify hosts on the Internet [2, 3]. It is implemented in a distributed database consisting of a hierarchy of nameservers. The name space is divided into zones and each zone has two or more authoritative nameservers that are responsible for keeping information about that zone up to date. One of these authoritative servers is the ....

....edit this file manually to make the new hosts public. The other authoritative servers (secondary servers) periodically fetch the contents of the master file in order to keep their records up to date. These zone transfers are done using the special zone transfer query type in DNS (AXFR query type [3]) When a client needs to obtain an IP address for a hostname, the query proceeds as shown in Fig. 1. In Fig. 1, is the host that the client is trying to resolve, and ### are DNS servers. First, the client sends the query to its local nameserver . Typically this local nameserver acts ....

P. V. Mockapetris, RFC 1035: Domain names --- implementation and specification, Nov. 1987.

....II. OVERVIEW OF DNS In this section we provide a brief overview of DNS and introduce some terminology that we shall use throughout the paper. The principle task of the DNS is to provide a mapping from the human readable domain names to numerical IP addresses used to identify hosts on the Internet [2, 3]. It is implemented in a distributed database consisting of a hierarchy of nameservers. The name space is divided into zones and each zone has two or more authoritative nameservers that are responsible for keeping information about that zone up to date. One of these authoritative servers is the ....

....D 4 H 1 6 7 8 2 3 4 5 Fig. 1. A DNS query. is the host that the client is trying to resolve, is the local nameserver, is a root name server, an intermediate nameserver, and is an authoritative nameserver for the queried host . type in DNS (AXFR query type [3]) When a client needs to obtain an IP address for a hostname, the query proceeds as shown in Fig. 1. In Fig. 1, is the host that the client is trying to resolve, and are DNS servers. First, the client sends the query to its local nameserver . Typically this local ....

P. V. Mockapetris, RFC 1035: Domain names --- implementation and specification, Nov. 1987.

....communityswitched to the Domain Name System. Paul Mockapetris was responsible for the design of the architecture of the new system. The original RFCs describing the Domain Name System are [Moc83a] and [Moc83b] They have been obsolete since the release of the current specifi, Moc87a] and [Moc87b] in November 1987 ( LR93] and [BG92] 2.3 Design Goals The effort of designing the Domain Name System was directed towards several goals, which had the main influence on determining the current structure. The aim was to create a system with the following objectives in mind: ffl Data ....

....the RDATA portion of the last three sections in a DNS message. These resource records are tagged according to the type of data they contain. Wemention only those types that provide necessary information for understanding this thesis. A complete list of types and classes can be found in RFC 1035 ([Moc87b]) ffl an A record contains a host address# a 32 bit Internet address when the class is IN ffl an NS record specifi, a host which should be authoritative for the specifi, class and domain ffl an SOA record is thefi rst entry in each of the databasefi,ta and specifi, a server to be ....

[Article contains additional citation context not shown here]

Paul Mockapetris. RFC-1035 Domain Names - Implementation and Specification. Network Working Group, November 1987.

....All of these problems arose because the original approach scaled poorly. In 1984 the network communityswitched to the Domain Name System. Paul Mockapetris was responsible for the design of the architecture of the new system. The original RFCs describing the Domain Name System are [Moc83a] and [Moc83b]. They have been obsolete since the release of the current specifi, Moc87a] and [Moc87b] in November 1987 ( LR93] and [BG92] 2.3 Design Goals The effort of designing the Domain Name System was directed towards several goals, which had the main influence on determining the current ....

Paul Mockapetris. RFC-883 Domain Names - Implementation and Specification. Network Working Group, November 1983.

....[49] and Grapevine [9] Optimistic replication is attractive for them for many reasons. First, they must replicate data over unreliable longhaul network links. Second, they often operate under a tight budget. Finally, data inconsistency is inherent in these services (e.g. HTTP [21] and DNS [52, 53] explicitly allow stale data to be presented to users) and using a replication algorithm with a loose consistency guarantee does not degrade their end to end service quality any more. Optimistic replication is a key enabling technology in mobile computing systems that need to replicate data on ....

P. V. Mockapetris. RFC1035: Domain names --- implementation and specification. http://info.internet.isi.edu/innotes /rfc/files/rfc1035.txt, November 1987.

....multiple mailboxes. Thus, a mail map actually maps a particular mailbox of a particular user to the list of nodes. The node that manages a user s profile also manages the mail maps for all the mailboxes for the user. 22 themselves on persistent storage (e.g. xFS [7] Active Directory [103] DNS [109, 110], and DDS [71] Unlike them, all the elements of FHC s naming service i.e. the user map, the profile, and mail maps are the soft state that resides only in nodes memories. After a node crashes, one of the remaining nodes computes the new user map by reassigning buckets managed by the ....

....for each object. It also should be quiescent ; that is, it should incur no computational overhead when no update is in progress for an object. Quick object deletion: Traditional replication algorithms assume that objects are long lived. Deleting objects often requires an off line intervention [109, 110, 147] or keeping residual records indefinitely [46, 103] This is in contrast with FHC s data (e.g. email messages and the user profile) which are created and deleted frequently. The algorithm needs to delete objects quickly without leaving any residual information behind. The key strategy we deploy ....

P. V. Mockapetris. RFC1035: Domain names --- implementation and specification. http://info.internet.isi.edu/in-notes/rfc/files/rfc1035.txt, November 1987. 4, 6.1

....As the size of the ARPAnet grew, the traffic for ftp process grew a lot. In 1984, Paul Mockapetris (who was assigned the responsibility for designing a new architecture) released two RFCs 882 and 883 describing the Domain Name System. These RFCs are then superseded by RFCs 1034 [4] and RFC 1035 [5]. These documents were augumented by many other RFCs which describe potential DNS security problems, methods for authorising domain data [3] mechanisms for dynamically updating name servers [1] secure dynamic update mechanisms [2] etc. Domain Name System is basically a hierarchial and ....

P Mockapetris. RFC 1035: Domain Names - Implementation and Specification. ftp://ftp.rfc-editor.org/in-notes/rfc1035.txt,Novermber 1987. 7

....the appropriate server it is necessary to extend and enhance the location mechanisms used for directing clients to these services. In the Internet it is fairly typical for a server to be identified by a name as opposed to a network address. Naming mechanisms such as the Domain Name System (DNS) [22] provide mappings from host names to their IP addresses. DNS can been used to map virtual host names (service names) to a set of IP addresses that correspond to the servers providing the replicated service [7] Take the case of a client making a Web access with a single name that is associated ....

P. Mockapetris. RFC 1035: Domain names --- implementation and specification, November 1987.

....II. OVERVIEW OF DNS In this section we provide a brief overview of DNS and introduce some terminology that we shall use throughout the paper. The principle task of the DNS is to provide a mapping from the human readable domain names to numerical IP addresses used to identify hosts on the Internet [2, 3]. It is implemented in a distributed database consisting of a hierarchy of nameservers. The name space is divided into zones and each zone has two or more authoritative nameservers that are responsible for keeping information about that zone up to date. One of these authoritative servers is the ....

....3 1 6 7 8 2 3 4 5 Fig. 1. A DNS query. C is the client, H is the host that the client is trying to resolve, D1 is the local nameserver, D2 is a root name server, D3 is an intermediate nameserver, and D 4 is an authoritative nameserver for the queried host H. type in DNS (AXFR query type [3]) When a client needs to obtain an IP address for a hostname, the query proceeds as shown in Fig. 1. In Fig. 1, C is the client, H is the host that the client is trying to resolve, and D 1 D 4 are DNS servers. First, the client sends the query to its local nameserver D 1 . Typically this ....

P. V. Mockapetris, RFC 1035: Domain names --- implementation and specification, Nov. 1987.

....as do any agents located through KNS name address resolution. However, new contacts in unrelated systems may not. 4.2 Agent Names The foundation of KNS is its agent naming scheme. It encompasses both symbolic and direct (URL based) names. The symbolic component is modeled after the DNS scheme [31, 32], and extends it to allow a URL to fill the root position of a name. A FQAN is defined as follows: GivenName # #a # zA# Z# # # ###; ### (1) NameIndex # # # ### # #### # ###; #### (2) LocalName # GivenName NameIndex (3) FQAN # # LocalName :# # # GivenName # LocalName # URL # (4) ....

P. Mockapetris. RFC 1035: Domain names - implementation and specification, 1987.

....to the appropriate server. To ensure the system can be used by the widest range of users, it is crucial that any method chosen must be completely transparent the client must not be forced to do anything special to benefit from the system. Walrus employs the standard name service of the Internet [10, 11] as its Director. Walrus uses the group communication capabilities of the Spread wide area group communication toolkit [14] to communicate between the Controllers and the Reporters. Spread is a system that provides multicast and group communications support to applications across local and wide ....

....usual statistics. PANIC similar to BYPASS, but requires notification to a human being. For example, a Web server process failure would result in a PANIC. 5. The Director Transparent Directing of Clients to Servers The Director is actually the standard distributed domain name system (DNS) [10, 11] used on the Internet without any changes. The Walrus system uses the DNS Round Trip Times method we proposed in [3] to transparently direct the user to the correct server. A brief recap of this method follows. A more complete description of this method and how it is used in Walrus is given in ....

P. Mockapetris. RFC-1035: Domain Names - Implementation and Specification. (1987).

....switched to the Domain Name System. Paul Mockapetris was responsible for the design of the architecture of the new system. The original RFCs 6 describing the Domain Name System are [Moc83a] and [Moc83b] They have been obsolete since the release of the current specifications [Moc87a] and [Moc87b] in November 1987 ( LR93] and [BG92] 2.3 Design Goals The effort of designing the Domain Name System was directed towards several goals, which had the main influence on determining the current structure. The aim was to create a system with the following objectives in mind: ffl Data Consistency ....

....the RDATA portion of the last three sections in a DNS message. These resource records are tagged according to the type of data they contain. We mention only those types that provide necessary information for understanding this thesis. A complete list of types and classes can be found in RFC 1035 ([Moc87b]) ffl an A record contains a host address; a 32 bit Internet address when the class is IN 18 ffl an NS record specifies a host which should be authoritative for the specified class and domain ffl an SOA record is the first entry in each of the database files and specifies a server to ....

[Article contains additional citation context not shown here]

Paul Mockapetris. RFC-1035 Domain Names - Implementation and Specification. Network Working Group, November 1987.

....All of these problems arose because the original approach scaled poorly. In 1984 the network community switched to the Domain Name System. Paul Mockapetris was responsible for the design of the architecture of the new system. The original RFCs 6 describing the Domain Name System are [Moc83a] and [Moc83b]. They have been obsolete since the release of the current specifications [Moc87a] and [Moc87b] in November 1987 ( LR93] and [BG92] 2.3 Design Goals The effort of designing the Domain Name System was directed towards several goals, which had the main influence on determining the current ....

Paul Mockapetris. RFC-883 Domain Names - Implementation and Specification. Network Working Group, November 1983.

....a complete set in an operating system. 6 Related Efforts There has been a great deal of research into caching. We restrict our discussion here to wide area network caching efforts. One of the earliest efforts to support caching in a wide area network environment was the Domain Naming System [16]. While not a general file or object cache, the DNS supports caching of name lookup results from server to server and also from client to server 9 , using timeouts for cache consistency. The hierarchical caching structure of the 9 The most common resolver client library implementation (BIND) ....

Paul Mockapetris. RFC 1035: Domain names - implementation and specification. Technical report, University of Southern California Information Sciences Institute, November 1987.

....a server optimized for running CGI scripts, and another server optimized for serving static text) While both servers may be identical replicas data wise, they still differ in their underlying capabilities. The DNS round trip times method This method utilizes the domain name system (DNS) 11] [12] to help determine which server is closest to the client. To explain this, a brief review of how a name to IP address lookup is done may be helpful: Fig. 1. Domain Name Service Resolution Every server on the Internet has a fully qualified domain name (FQDN) FQDN are usually read from left to ....

Mockapetris, P.: RFC-1035: Domain Names -- Implementation and Specification. (1987).

No context found.

P. Mockapetris. RFC 1035 - Domain Names - Implementation and Specification, November 1987.

No context found.

P. V. Mockapetris. RFC 1035: Domain names --- implementation and specification, Nov. 1987.

No context found.

P. V. Mockapetris. RFC 1035: Domain names --- implementation and specification, Nov. 1987.

No context found.

P. Mockapetris. Rfc 1035: Domain names - implementation and specification. , 1987.

No context found.

P. V. Mockapetris. RFC 1035: Domain names --- implementation and specification. IETF, November 1987. ftp://ftp.ietf.org/rfc/rfc1035.txt.

No context found.

P. V. Mockapetris, RFC 1035: Domain names --- implementation and specification, Nov. 1987.

No context found.

P. Mockapetris. RFC-1035: Domain Names - Implementation and Specification. (1987).

No context found.

Mockapetris, P.: RFC-1035: Domain Names - Implementation and Specification. (1987).

First 50 documents

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC