📄 00000004.htm
字号:
referrals to other name servers. The domain system also defines <BR>procedures for caching retrieved data and for periodic refreshing of <BR>data defined by the system administrator. <BR> <BR>The system administrators provide: <BR> <BR> - The definition of zone boundaries. <BR> <BR> - Master files of data. <BR> <BR> - Updates to master files. <BR> <BR> - Statements of the refresh policies desired. <BR> <BR>The domain system provides: <BR> <BR> - Standard formats for resource data. <BR> <BR> - Standard methods for querying the database. <BR> <BR> - Standard methods for name servers to refresh local data from <BR> foreign name servers. <BR> <BR> <BR> <BR> <BR> <BR>Mockapetris [Page 5] <BR> <BR>RFC 1034 Domain Concepts and Facilities November 1987 <BR> <BR> <BR>2.4. Elements of the DNS <BR> <BR>The DNS has three major components: <BR> <BR> - The DOMAIN NAME SPACE and RESOURCE RECORDS, which are <BR> specifications for a tree structured name space and data <BR> associated with the names. Conceptually, each node and leaf <BR> of the domain name space tree names a set of information, and <BR> query operations are attempts to extract specific types of <BR> information from a particular set. A query names the domain <BR> name of interest and describes the type of resource <BR> information that is desired. For example, the Internet <BR> uses some of its domain names to identify hosts; queries for <BR> address resources return Internet host addresses. <BR> <BR> - NAME SERVERS are server programs which hold information about <BR> the domain tree's structure and set information. A name <BR> server may cache structure or set information about any part <BR> of the domain tree, but in general a particular name server <BR> has complete information about a subset of the domain space, <BR> and pointers to other name servers that can be used to lead to <BR> information from any part of the domain tree. Name servers <BR> know the parts of the domain tree for which they have complete <BR> information; a name server is said to be an AUTHORITY for <BR> these parts of the name space. Authoritative information is <BR> organized into units called ZONEs, and these zones can be <BR> automatically distributed to the name servers which provide <BR> redundant service for the data in a zone. <BR> <BR> - RESOLVERS are programs that extract information from name <BR> servers in response to client requests. Resolvers must be <BR> able to access at least one name server and use that name <BR> server's information to answer a query directly, or pursue the <BR> query using referrals to other name servers. A resolver will <BR> typically be a system routine that is directly accessible to <BR> user programs; hence no protocol is necessary between the <BR> resolver and the user program. <BR> <BR>These three components roughly correspond to the three layers or views <BR>of the domain system: <BR> <BR> - From the user's point of view, the domain system is accessed <BR> through a simple procedure or OS call to a local resolver. <BR> The domain space consists of a single tree and the user can <BR> request information from any section of the tree. <BR> <BR> - From the resolver's point of view, the domain system is <BR> composed of an unknown number of name servers. Each name <BR> <BR> <BR> <BR>Mockapetris [Page 6] <BR> <BR>RFC 1034 Domain Concepts and Facilities November 1987 <BR> <BR> <BR> server has one or more pieces of the whole domain tree's data, <BR> but the resolver views each of these databases as essentially <BR> static. <BR> <BR> - From a name server's point of view, the domain system consists <BR> of separate sets of local information called zones. The name <BR> server has local copies of some of the zones. The name server <BR> must periodically refresh its zones from master copies in <BR> local files or foreign name servers. The name server must <BR> concurrently process queries that arrive from resolvers. <BR> <BR>In the interests of performance, implementations may couple these <BR>functions. For example, a resolver on the same machine as a name server <BR>might share a database consisting of the the zones managed by the name <BR>server and the cache managed by the resolver. <BR> <BR>3. DOMAIN NAME SPACE and RESOURCE RECORDS <BR> <BR>3.1. Name space specifications and terminology <BR> <BR>The domain name space is a tree structure. Each node and leaf on the <BR>tree corresponds to a resource set (which may be empty). The domain <BR>system makes no distinctions between the uses of the interior nodes and <BR>leaves, and this memo uses the term "node" to refer to both. <BR> <BR>Each node has a label, which is zero to 63 octets in length. Brother <BR>nodes may not have the same label, although the same label can be used <BR>for nodes which are not brothers. One label is reserved, and that is <BR>the null (i.e., zero length) label used for the root. <BR> <BR>The domain name of a node is the list of the labels on the path from the <BR>node to the root of the tree. By convention, the labels that compose a <BR>domain name are printed or read left to right, from the most specific <BR>(lowest, farthest from the root) to the least specific (highest, closest <BR>to the root). <BR> <BR>Internally, programs that manipulate domain names should represent them <BR>as sequences of labels, where each label is a length octet followed by <BR>an octet string. Because all domain names end at the root, which has a <BR>null string for a label, these internal representations can use a length <BR>byte of zero to terminate a domain name. <BR>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -