Connected: An Internet Encyclopedia
RFC 1034

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments

Search: |  | Search Depth: |
Search Type: | String RegEx | Search Options: | NoCase WholeWord

Next: 2. INTRODUCTION

Network Working Group
Request for Comments: 1034
Obsoletes: RFCs 882, 883, 973

P. Mockapetris
ISI
November 1987

### DOMAIN NAMES - CONCEPTS AND FACILITIES

### 1. STATUS OF THIS MEMO

This RFC is an introduction to the Domain Name System (DNS), and omits many details which can be found in a companion RFC, "Domain Names - Implementation and Specification" [RFC-1035]. That RFC assumes that the reader is familiar with the concepts discussed in this memo.

A subset of DNS functions and data types constitute an official protocol. The official protocol includes standard queries and their responses and most of the Internet class data formats (e.g., host addresses).

However, the domain system is intentionally extensible. Researchers are continuously proposing, implementing and experimenting with new data types, query types, classes, functions, etc. Thus while the components of the official protocol are expected to stay essentially unchanged and operate as a production service, experimental behavior should always be expected in extensions beyond the official protocol. Experimental or obsolete features are clearly marked in these RFCs, and such information should be used with caution.

The reader is especially cautioned not to depend on the values which appear in examples to be current or complete, since their purpose is primarily pedagogical. Distribution of this memo is unlimited.

### Table of Contents

1. STATUS OF THIS MEMO
2. INTRODUCTION

2.1. The history of domain names
2.2. DNS design goals
2.3. Assumptions about usage
2.4. Elements of the DNS

3. DOMAIN NAME SPACE and RESOURCE RECORDS

3.1. Name space specifications and terminology
3.2. Administrative guidelines on use
3.3. Technical guidelines on use
3.4. Example name space
3.5. Preferred name syntax
3.6. Resource Records

3.6.1. Textual expression of RRs
3.6.2. Aliases and canonical names

3.7. Queries

3.7.1. Standard queries
3.7.2. Inverse queries (Optional)

3.8. Status queries (Experimental)
3.9. Completion queries (Obsolete)

4. NAME SERVERS

4.1. Introduction
4.2. How the database is divided into zones

4.2.1. Technical considerations
4.2.2. Administrative considerations

4.3. Name server internals

4.3.1. Queries and responses
4.3.2. Algorithm
4.3.3. Wildcards
4.3.4. Negative response caching (Optional)
4.3.5. Zone maintenance and transfers

5. RESOLVERS

5.1. Introduction
5.2. Client-resolver interface

5.2.1. Typical functions
5.2.2. Aliases
5.2.3. Temporary failures

5.3. Resolver internals

5.3.1. Stub resolvers
5.3.2. Resources
5.3.3. Algorithm

6. A SCENARIO

6.1. C.ISI.EDU name server
6.2. Example standard queries

6.2.1. QNAME=SRI-NIC.ARPA, QTYPE=A
6.2.2. QNAME=SRI-NIC.ARPA, QTYPE=*
6.2.3. QNAME=SRI-NIC.ARPA, QTYPE=MX
6.2.4. QNAME=SRI-NIC.ARPA, QTYPE=NS
6.2.5. QNAME=SIR-NIC.ARPA, QTYPE=A
6.2.6. QNAME=BRL.MIL, QTYPE=A
6.2.7. QNAME=USC-ISIC.ARPA, QTYPE=A
6.2.8. QNAME=USC-ISIC.ARPA, QTYPE=CNAME

6.3. Example resolution

6.3.1. Resolve MX for ISI.EDU.
6.3.2. Get the host name for address 26.6.0.65
6.3.3. Get the host address of poneria.ISI.EDU

7. REFERENCES and BIBLIOGRAPHY

Original text document

Next: 2. INTRODUCTION

Connected: An Internet Encyclopedia
RFC 1034