📄 00000004.htm
字号:
design also must take into account the scheme for mail exchanges [RFC- <BR>974]. <BR> <BR>The typical user is not concerned with defining these rules, but should <BR>understand that they usually are the result of numerous compromises <BR>between desires for upward compatibility with old usage, interactions <BR>between different object definitions, and the inevitable urge to add new <BR>features when defining the rules. The way the DNS is used to support <BR>some object is often more crucial than the restrictions inherent in the <BR>DNS. <BR> <BR>3.4. Example name space <BR> <BR>The following figure shows a part of the current domain name space, and <BR>is used in many examples in this RFC. Note that the tree is a very <BR>small subset of the actual name space. <BR> <BR> | <BR> | <BR> +---------------------+------------------+ <BR> | | | <BR> MIL EDU ARPA <BR> | | | <BR> | | | <BR> +-----+-----+ | +------+-----+-----+ <BR> | | | | | | | <BR> BRL NOSC DARPA | IN-ADDR SRI-NIC ACC <BR> | <BR> +--------+------------------+---------------+--------+ <BR> | | | | | <BR> UCI MIT | UDEL YALE <BR> | ISI <BR> | | <BR> +---+---+ | <BR> | | | <BR> LCS ACHILLES +--+-----+-----+--------+ <BR> | | | | | | <BR> XX A C VAXA VENERA Mockapetris <BR> <BR>In this example, the root domain has three immediate subdomains: MIL, <BR>EDU, and ARPA. The LCS.MIT.EDU domain has one immediate subdomain named <BR>XX.LCS.MIT.EDU. All of the leaves are also domains. <BR> <BR>3.5. Preferred name syntax <BR> <BR>The DNS specifications attempt to be as general as possible in the rules <BR> <BR> <BR> <BR>Mockapetris [Page 10] <BR> <BR>RFC 1034 Domain Concepts and Facilities November 1987 <BR> <BR> <BR>for constructing domain names. The idea is that the name of any <BR>existing object can be expressed as a domain name with minimal changes. <BR>However, when assigning a domain name for an object, the prudent user <BR>will select a name which satisfies both the rules of the domain system <BR>and any existing rules for the object, whether these rules are published <BR>or implied by existing programs. <BR> <BR>For example, when naming a mail domain, the user should satisfy both the <BR>rules of this memo and those in RFC-822. When creating a new host name, <BR>the old rules for HOSTS.TXT should be followed. This avoids problems <BR>when old software is converted to use domain names. <BR> <BR>The following syntax will result in fewer problems with many <BR>applications that use domain names (e.g., mail, TELNET). <BR> <BR><domain> ::= <subdomain> | " " <BR> <BR><subdomain> ::= <label> | <subdomain> "." <label> <BR> <BR><label> ::= <letter> [ [ <ldh-str> ] <let-dig> ] <BR> <BR><ldh-str> ::= <let-dig-hyp> | <let-dig-hyp> <ldh-str> <BR> <BR><let-dig-hyp> ::= <let-dig> | "-" <BR> <BR><let-dig> ::= <letter> | <digit> <BR> <BR><letter> ::= any one of the 52 alphabetic characters A through Z in <BR>upper case and a through z in lower case <BR> <BR><digit> ::= any one of the ten digits 0 through 9 <BR> <BR>Note that while upper and lower case letters are allowed in domain <BR>names, no significance is attached to the case. That is, two names with <BR>the same spelling but different case are to be treated as if identical. <BR> <BR>The labels must follow the rules for ARPANET host names. They must <BR>start with a letter, end with a letter or digit, and have as interior <BR>characters only letters, digits, and hyphen. There are also some <BR>restrictions on the length. Labels must be 63 characters or less. <BR> <BR>For example, the following strings identify hosts in the Internet: <BR> <BR>A.ISI.EDU XX.LCS.MIT.EDU SRI-NIC.ARPA <BR> <BR>3.6. Resource Records <BR> <BR>A domain name identifies a node. Each node has a set of resource <BR> <BR> <BR> <BR>Mockapetris [Page 11] <BR> <BR>RFC 1034 Domain Concepts and Facilities November 1987 <BR> <BR> <BR>information, which may be empty. The set of resource information <BR>associated with a particular name is composed of separate resource <BR>records (RRs). The order of RRs in a set is not significant, and need <BR>not be preserved by name servers, resolvers, or other parts of the DNS. <BR> <BR>When we talk about a specific RR, we assume it has the following: <BR> <BR>owner which is the domain name where the RR is found. <BR> <BR>type which is an encoded 16 bit value that specifies the type <BR> of the resource in this resource record. Types refer to <BR> abstract resources. <BR> <BR> This memo uses the following types: <BR> <BR> &nbs
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -