📄 rfc1035.4up.ps
字号:
0 -392 translate0.490859 dup scale/pagenum 1 def/fname (/usr/local/share/doc/rfc/Mirrors/ftp.isi.edu/in-notes/rfc1035.txt) def/fdir (/usr/local/share/doc/rfc/Mirrors/ftp.isi.edu/in-notes/) def/ftail (rfc1035.txt) def% User defined strings:/fmodstr (Tue Nov 24 00:00:00 1987) def/pagenumstr (1) def/user_header_p true def/user_header_left_str (RFC1035) def/user_header_center_str (RFC.net) def/user_header_right_str (Page 1 of 56) def%%EndPageSetupdo_header5 764 M(Network Working Group P. Mockapetris) s5 751 M(Request for Comments: 1035 ISI) s5 738 M( November 1987) s5 725 M(Obsoletes: RFCs 882, 883, 973) s5 699 M( DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION) s5 660 M(1. STATUS OF THIS MEMO) s5 634 M(This RFC describes the details of the domain system and protocol, and) s5 621 M(assumes that the reader is familiar with the concepts discussed in a) s5 608 M(companion RFC, "Domain Names - Concepts and Facilities" [RFC-1034].) s5 582 M(The domain system is a mixture of functions and data types which are an) s5 569 M(official protocol and functions and data types which are still) s5 556 M(experimental. Since the domain system is intentionally extensible, new) s5 543 M(data types and experimental behavior should always be expected in parts) s5 530 M(of the system beyond the official protocol. The official protocol parts) s5 517 M(include standard queries, responses and the Internet class RR data) s5 504 M(formats \(e.g., host addresses\). Since the previous RFC set, several) s5 491 M(definitions have changed, so some previous definitions are obsolete.) s5 465 M(Experimental or obsolete features are clearly marked in these RFCs, and) s5 452 M(such information should be used with caution.) s5 426 M(The reader is especially cautioned not to depend on the values which) s5 413 M(appear in examples to be current or complete, since their purpose is) s5 400 M(primarily pedagogical. Distribution of this memo is unlimited.) s5 374 M( Table of Contents) s5 348 M( 1. STATUS OF THIS MEMO 1) s5 335 M( 2. INTRODUCTION 3) s5 322 M( 2.1. Overview 3) s5 309 M( 2.2. Common configurations 4) s5 296 M( 2.3. Conventions 7) s5 283 M( 2.3.1. Preferred name syntax 7) s5 270 M( 2.3.2. Data Transmission Order 8) s5 257 M( 2.3.3. Character Case 9) s5 244 M( 2.3.4. Size limits 10) s5 231 M( 3. DOMAIN NAME SPACE AND RR DEFINITIONS 10) s5 218 M( 3.1. Name space definitions 10) s5 205 M( 3.2. RR definitions 11) s5 192 M( 3.2.1. Format 11) s5 179 M( 3.2.2. TYPE values 12) s5 166 M( 3.2.3. QTYPE values 12) s5 153 M( 3.2.4. CLASS values 13) s5 101 M(Mockapetris [Page 1]) s_R%Page: (2) 2%BeginPageSetup_S% N-up sub-page 2/4278 -392 translate0.490859 dup scale/pagenum 2 def/fname (/usr/local/share/doc/rfc/Mirrors/ftp.isi.edu/in-notes/rfc1035.txt) def/fdir (/usr/local/share/doc/rfc/Mirrors/ftp.isi.edu/in-notes/) def/ftail (rfc1035.txt) def% User defined strings:/fmodstr (Tue Nov 24 00:00:00 1987) def/pagenumstr (2) def/user_header_p true def/user_header_left_str (RFC1035) def/user_header_center_str (RFC.net) def/user_header_right_str (Page 2 of 56) def%%EndPageSetupdo_header5 751 M(RFC 1035 Domain Implementation and Specification November 1987) s5 712 M( 3.2.5. QCLASS values 13) s5 699 M( 3.3. Standard RRs 13) s5 686 M( 3.3.1. CNAME RDATA format 14) s5 673 M( 3.3.2. HINFO RDATA format 14) s5 660 M( 3.3.3. MB RDATA format \(EXPERIMENTAL\) 14) s5 647 M( 3.3.4. MD RDATA format \(Obsolete\) 15) s5 634 M( 3.3.5. MF RDATA format \(Obsolete\) 15) s5 621 M( 3.3.6. MG RDATA format \(EXPERIMENTAL\) 16) s5 608 M( 3.3.7. MINFO RDATA format \(EXPERIMENTAL\) 16) s5 595 M( 3.3.8. MR RDATA format \(EXPERIMENTAL\) 17) s5 582 M( 3.3.9. MX RDATA format 17) s5 569 M( 3.3.10. NULL RDATA format \(EXPERIMENTAL\) 17) s5 556 M( 3.3.11. NS RDATA format 18) s5 543 M( 3.3.12. PTR RDATA format 18) s5 530 M( 3.3.13. SOA RDATA format 19) s5 517 M( 3.3.14. TXT RDATA format 20) s5 504 M( 3.4. ARPA Internet specific RRs 20) s5 491 M( 3.4.1. A RDATA format 20) s5 478 M( 3.4.2. WKS RDATA format 21) s5 465 M( 3.5. IN-ADDR.ARPA domain 22) s5 452 M( 3.6. Defining new types, classes, and special namespaces 24) s5 439 M( 4. MESSAGES 25) s5 426 M( 4.1. Format 25) s5 413 M( 4.1.1. Header section format 26) s5 400 M( 4.1.2. Question section format 28) s5 387 M( 4.1.3. Resource record format 29) s5 374 M( 4.1.4. Message compression 30) s5 361 M( 4.2. Transport 32) s5 348 M( 4.2.1. UDP usage 32) s5 335 M( 4.2.2. TCP usage 32) s5 322 M( 5. MASTER FILES 33) s5 309 M( 5.1. Format 33) s5 296 M( 5.2. Use of master files to define zones 35) s5 283 M( 5.3. Master file example 36) s5 270 M( 6. NAME SERVER IMPLEMENTATION 37) s5 257 M( 6.1. Architecture 37) s5 244 M( 6.1.1. Control 37) s5 231 M( 6.1.2. Database 37) s5 218 M( 6.1.3. Time 39) s5 205 M( 6.2. Standard query processing 39) s5 192 M( 6.3. Zone refresh and reload processing 39) s5 179 M( 6.4. Inverse queries \(Optional\) 40) s5 166 M( 6.4.1. The contents of inverse queries and responses 40) s5 153 M( 6.4.2. Inverse query and response example 41) s5 140 M( 6.4.3. Inverse query processing 42) s5 49 M(Mockapetris [Page 2]) s_R%Page: (3) 3%BeginPageSetup_S% N-up sub-page 3/40 -794 translate0.490859 dup scale/pagenum 3 def/fname (/usr/local/share/doc/rfc/Mirrors/ftp.isi.edu/in-notes/rfc1035.txt) def/fdir (/usr/local/share/doc/rfc/Mirrors/ftp.isi.edu/in-notes/) def/ftail (rfc1035.txt) def% User defined strings:/fmodstr (Tue Nov 24 00:00:00 1987) def/pagenumstr (3) def/user_header_p true def/user_header_left_str (RFC1035) def/user_header_center_str (RFC.net) def/user_header_right_str (Page 3 of 56) def%%EndPageSetupdo_header5 751 M(RFC 1035 Domain Implementation and Specification November 1987) s5 712 M( 6.5. Completion queries and responses 42) s5 699 M( 7. RESOLVER IMPLEMENTATION 43) s5 686 M( 7.1. Transforming a user request into a query 43) s5 673 M( 7.2. Sending the queries 44) s5 660 M( 7.3. Processing responses 46) s5 647 M( 7.4. Using the cache 47) s5 634 M( 8. MAIL SUPPORT 47) s5 621 M( 8.1. Mail exchange binding 48) s5 608 M( 8.2. Mailbox binding \(Experimental\) 48) s5 595 M( 9. REFERENCES and BIBLIOGRAPHY 50) s5 582 M( Index 54) s5 556 M(2. INTRODUCTION) s5 530 M(2.1. Overview) s5 504 M(The goal of domain names is to provide a mechanism for naming resources) s5 491 M(in such a way that the names are usable in different hosts, networks,) s5 478 M(protocol families, internets, and administrative organizations.) s5 452 M(From the user's point of view, domain names are useful as arguments to a) s5 439 M(local agent, called a resolver, which retrieves information associated) s5 426 M(with the domain name. Thus a user might ask for the host address or) s5 413 M(mail information associated with a particular domain name. To enable) s5 400 M(the user to request a particular type of information, an appropriate) s5 387 M(query type is passed to the resolver with the domain name. To the user,) s5 374 M(the domain tree is a single information space; the resolver is) s5 361 M(responsible for hiding the distribution of data among name servers from) s5 348 M(the user.) s5 322 M(From the resolver's point of view, the database that makes up the domain) s5 309 M(space is distributed among various name servers. Different parts of the) s5 296 M(domain space are stored in different name servers, although a particular) s5 283 M(data item will be stored redundantly in two or more name servers. The) s5 270 M(resolver starts with knowledge of at least one name server. When the) s5 257 M(resolver processes a user query it asks a known name server for the) s5 244 M(information; in return, the resolver either receives the desired) s5 231 M(information or a referral to another name server. Using these) s5 218 M(referrals, resolvers learn the identities and contents of other name) s5 205 M(servers. Resolvers are responsible for dealing with the distribution of) s5 192 M(the domain space and dealing with the effects of name server failure by) s5 179 M(consulting redundant databases in other servers.) s5 153 M(Name servers manage two kinds of data. The first kind of data held in) s5 140 M(sets called zones; each zone is the complete database for a particular) s5 127 M("pruned" subtree of the domain space. This data is called) s5 114 M(authoritative. A name server periodically checks to make sure that its) s5 101 M(zones are up to date, and if not, obtains a new copy of updated zones) s5 49 M(Mockapetris [Page 3]) s_R%Page: (4) 4%BeginPageSetup_S% N-up sub-page 4/4278 -794 translate0.490859 dup scale/pagenum 4 def/fname (/usr/local/share/doc/rfc/Mirrors/ftp.isi.edu/in-notes/rfc1035.txt) def/fdir (/usr/local/share/doc/rfc/Mirrors/ftp.isi.edu/in-notes/) def/ftail (rfc1035.txt) def% User defined strings:/fmodstr (Tue Nov 24 00:00:00 1987) def/pagenumstr (4) def/user_header_p true def/user_header_left_str (RFC1035) def/user_header_center_str (RFC.net) def/user_header_right_str (Page 4 of 56) def%%EndPageSetupdo_header5 751 M(RFC 1035 Domain Implementation and Specification November 1987) s5 712 M(from master files stored locally or in another name server. The second) s5 699 M(kind of data is cached data which was acquired by a local resolver.) s5 686 M(This data may be incomplete, but improves the performance of the) s5 673 M(retrieval process when non-local data is repeatedly accessed. Cached) s5 660 M(data is eventually discarded by a timeout mechanism.) s5 634 M(This functional structure isolates the problems of user interface,) s5 621 M(failure recovery, and distribution in the resolvers and isolates the) s5 608 M(database update and refresh problems in the name servers.) s5 582 M(2.2. Common configurations) s5 556 M(A host can participate in the domain name system in a number of ways,) s5 543 M(depending on whether the host runs programs that retrieve information) s5 530 M(from the domain system, name servers that answer queries from other) s5 517 M(hosts, or various combinations of both functions. The simplest, and) s5 504 M(perhaps most typical, configuration is shown below:) s5 478 M( Local Host | Foreign) s5 465 M( |) s5 452 M( +---------+ +----------+ | +--------+) s5 439 M( | | user queries | |queries | | |) s5 426 M( | User |-------------->| |---------|->|Foreign |) s5 413 M( | Program | | Resolver | | | Name |) s5 400 M( | |<--------------| |<--------|--| Server |) s5 387 M( | | user responses| |responses| | |) s5 374 M( +---------+ +----------+ | +--------+) s5 361 M( | A |) s5 348 M( cache additions | | references |) s5 335 M( V | |) s5 322 M( +----------+ |) s5 309 M( | cache | |) s5 296 M( +----------+ |) s5 270 M(User programs interact with the domain name space through resolvers; the) s5 257 M(format of user queries and user responses is specific to the host and) s5 244 M(its operating system. User queries will typically be operating system) s5 231 M(calls, and the resolver and its cache will be part of the host operating) s5 218 M(system. Less capable hosts may choose to implement the resolver as a) s5 205 M⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -