RFC 1035:DOMAIN NAMES - IMPLEMENTATION AND SPECIFI...
RFC-Ref

DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION


1. STATUS
2. INTRODUCTION
2.1. Overview
2.2. Common configurations
2.3. Conventions
2.3.1. Preferred name syntax
2.3.2. Data Transmission Order
2.3.3. Character Case
2.3.4. Size limits
3. DOMAIN NAME SPACE AND RR DEFINITIONS
3.1. Name space definitions
3.2. RR definitions
3.2.1. Format
3.2.2. TYPE values
3.2.3. QTYPE values
3.2.4. CLASS values
3.2.5. QCLASS values
3.3. Standard RRs
3.3.1. CNAME RDATA format
3.3.2. HINFO RDATA format
3.3.3. MB RDATA format (EXPERIMENTAL)
3.3.4. MD RDATA format (Obsolete)
3.3.5. MF RDATA format (Obsolete)
3.3.6. MG RDATA format (EXPERIMENTAL)
3.3.7. MINFO RDATA format (EXPERIMENTAL)
3.3.8. MR RDATA format (EXPERIMENTAL)
3.3.9. MX RDATA format
3.3.10. NULL RDATA format (EXPERIMENTAL)
3.3.11. NS RDATA format
3.3.12. PTR RDATA format
3.3.13. SOA RDATA format
3.3.14. TXT RDATA format
3.4. Internet specific RRs
3.4.1. A RDATA format
3.4.2. WKS RDATA format
3.5. IN-ADDR.ARPA domain
3.6. Defining new types, classes, and special namespaces
4. MESSAGES
4.1. Format
4.1.1. Header section format
4.1.2. Question section format
4.1.3. Resource record format
4.1.4. Message compression
4.2. Transport
4.2.1. UDP usage
4.2.2. TCP usage
5. MASTER FILES
5.1. Format
5.2. Use of master files to define zones
5.3. Master file example
6. NAME SERVER IMPLEMENTATION
6.1. Architecture
6.1.1. Control
6.1.2. Database
6.1.3. Time
6.2. Standard query processing
6.3. Zone refresh and reload processing
6.4. Inverse queries (Optional)
6.4.1. The contents of inverse queries and responses
6.4.2. Inverse query and response example
6.4.3. Inverse query processing
6.5. Completion queries and responses
7. RESOLVER IMPLEMENTATION
7.1. Transforming a user request into a query
7.2. Sending the queries
7.3. Processing responses
7.4. Using the cache
8. MAIL SUPPORT
8.1. Mail exchange binding
8.2. Mailbox binding (Experimental)
9. REFERENCES and BIBLIOGRAPHY

Google
Web
RFC-Ref