ACM Home Page
Please provide us with feedback. Feedback
Development of the domain name system
Full text PdfPdf (1.24 MB)
Source Applications, Technologies, Architectures, and Protocols for Computer Communication archive
Symposium proceedings on Communications architectures and protocols table of contents
Stanford, California, United States
Pages: 123 - 133  
Year of Publication: 1988
ISBN:0-89791-279-9
Also published in ...
Authors
P. Mockapetris  Univ. of Southern California, Marina del Rey
K. J. Dunlap  Digital Equipment Corp., Washington
Sponsors
SIGCOMM: ACM Special Interest Group on Data Communication
SRI Intl :
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 12,   Downloads (12 Months): 126,   Citation Count: 53
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/52324.52338
What is a DOI?

ABSTRACT

The Domain Name System (DNS) provides name service for the DARPA Internet. It is one of the largest name services in operation today, serves a highly diverse community of hosts, users, and networks, and uses a unique combination of hierarchies, caching, and datagram access. This paper examines the ideas behind the initial design of the DNS in 1983, discusses the evolution of these ideas into the current implementations and usages, notes conspicuous surprises, successes and shortcomings, and attempts to predict its future evolution.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

Birrell 82
 
Dunlap 86a
Dunlap, K. J., Bloom, J. M., "Experiences Implementing BIND, A Distributed Name Server for the DARPA Internet",Proceedings USENIX Summer Conference, Atlanta, Georgia. June 1986, pages 172-181.
 
Dunlap 86b
Dunlap, K. J., "Name Server Operations Guide for BIND", Unix System Manager's Manual, SMM-11. 4.3 Berkeley Software Distribution, Virtual VAX-11 Version. University of California. April 1986.
 
IEN 116
Postel, Jon, "Internet Name Server'', iEN 116, August 1979.
 
Larson 85
Larson, Personal communication.
Mills 88
Oppen 83
Quarterman 86
 
RFC 882
P. Mockapetris, "Domain names - Concepts and Facilities," RFC 882, USC/Information Sciences Institute, November 1983. (Obsolete, superseded by RFC 1034.)
 
RFC 883
P. Mockapetris, "Domain names - Implementation and Specification,'' RFC 883, USC/Information Sciences Institute, November 1983. (Obsolete, superseded by RFC 1035.)
 
RFC 920
Postel, Jon, and Reynolds, Joyce, "Domain Requirements", RFC 920, October 1984.
 
RFC 973
Mockapetris, Paul V., "Domain System Changes and Observations'', RFC 973, January 1986.
 
RFC 974
Partridge, Craig, "Mail Routing and the Domain System", RFC 974, January 1986.
 
RFC 1031
W. Lazear, "MILNET Name Domain Transition", RFC 1031, November 1987.
 
RFC 1034
P. Mockapetris, "Domain names - Concepts and Facilities," RFC 1034, USC/Information Sciences Institute, November 1987.
 
RFC 1035
P. Mockapetris, "Domain names - Implementation and Specification,'' RFC 1035, USC/Information Sciences Institute, November 1987.
 
Stahl 87
M. Stahl, "DDN Domain Naming - Administration, Registration, Procedures and Policy", Second TCP/IP Interoperability Conference, December, 1987.

CITED BY  53

Collaborative Colleagues:
P. Mockapetris: colleagues
K. J. Dunlap: colleagues