📄 00000003.htm
字号:
<HTML><HEAD> <TITLE>BBS水木清华站∶精华区</TITLE></HEAD><BODY><CENTER><H1>BBS水木清华站∶精华区</H1></CENTER>Network Working Group M. Stahl <BR>Request for Comments: 1032 SRI International <BR> November 1987 <BR> <BR> <BR> DOMAIN ADMINISTRATORS GUIDE <BR> <BR> <BR>STATUS OF THIS MEMO <BR> <BR> This memo describes procedures for registering a domain with the <BR> Network Information Center (NIC) of Defense Data Network (DDN), and <BR> offers guidelines on the establishment and administration of a domain <BR> in accordance with the requirements specified in RFC-920. It is <BR> intended for use by domain administrators. This memo should be used <BR> in conjunction with RFC-920, which is an official policy statement of <BR> the Internet Activities Board (IAB) and the Defense Advanced Research <BR> Projects Agency (DARPA). Distribution of this memo is unlimited. <BR> <BR>BACKGROUND <BR> <BR> Domains are administrative entities that provide decentralized <BR> management of host naming and addressing. The domain-naming system <BR> is distributed and hierarchical. <BR> <BR> The NIC is designated by the Defense Communications Agency (DCA) to <BR> provide registry services for the domain-naming system on the DDN and <BR> DARPA portions of the Internet. <BR> <BR> As registrar of top-level and second-level domains, as well as <BR> administrator of the root domain name servers on behalf of DARPA and <BR> DDN, the NIC is responsible for maintaining the root server zone <BR> files and their binary equivalents. In addition, the NIC is <BR> responsible for administering the top-level domains of "ARPA," "COM," <BR> "EDU," "ORG," "GOV," and "MIL" on behalf of DCA and DARPA until it <BR> becomes feasible for other appropriate organizations to assume those <BR> responsibilities. <BR> <BR> It is recommended that the guidelines described in this document be <BR> used by domain administrators in the establishment and control of <BR> second-level domains. <BR> <BR>THE DOMAIN ADMINISTRATOR <BR> <BR> The role of the domain administrator (DA) is that of coordinator, <BR> manager, and technician. If his domain is established at the second <BR> level or lower in the tree, the DA must register by interacting with <BR> the management of the domain directly above his, making certain that <BR> <BR> <BR> <BR>Stahl [Page 1] <BR> <BR>RFC 1032 DOMAIN ADMINISTRATORS GUIDE November 1987 <BR> <BR> <BR> his domain satisfies all the requirements of the administration under <BR> which his domain would be situated. To find out who has authority <BR> over the name space he wishes to join, the DA can ask the NIC <BR> Hostmaster. Information on contacts for the top-level and second- <BR> level domains can also be found on line in the file NETINFO:DOMAIN- <BR> CONTACTS.TXT, which is available from the NIC via anonymous FTP. <BR> <BR> The DA should be technically competent; he should understand the <BR> concepts and procedures for operating a domain server, as described <BR> in RFC-1034, and make sure that the service provided is reliable and <BR> uninterrupted. It is his responsibility or that of his delegate to <BR> ensure that the data will be current at all times. As a manager, the <BR> DA must be able to handle complaints about service provided by his <BR> domain name server. He must be aware of the behavior of the hosts in <BR> his domain, and take prompt action on reports of problems, such as <BR> protocol violations or other serious misbehavior. The administrator <BR> of a domain must be a responsible person who has the authority to <BR> either enforce these actions himself or delegate them to someone <BR> else. <BR> <BR> Name assignments within a domain are controlled by the DA, who should <BR> verify that names are unique within his domain and that they conform <BR> to standard naming conventions. He furnishes access to names and <BR> name-related information to users both inside and outside his domain. <BR> He should work closely with the personnel he has designated as the <BR> "technical and zone" contacts for his domain, for many administrative <BR> decisions will be made on the basis of input from these people. <BR> <BR>THE DOMAIN TECHNICAL AND ZONE CONTACT <BR> <BR> A zone consists of those contiguous parts of the domain tree for <BR> which a domain server has complete information and over which it has <BR> authority. A domain server may be authoritative for more than one <BR> zone. The domain technical/zone contact is the person who tends to <BR> the technical aspects of maintaining the domain's name server and <BR> resolver software, and database files. He keeps the name server <BR> running, and interacts with technical people in other domains and <BR> zones to solve problems that affect his zone. <BR> <BR>POLICIES <BR> <BR> Domain or host name choices and the allocation of domain name space <BR> are considered to be local matters. In the event of conflicts, it is <BR> the policy of the NIC not to get involved in local disputes or in the <BR> local decision-making process. The NIC will not act as referee in <BR> disputes over such matters as who has the "right" to register a <BR> particular top-level or second-level domain for an organization. The <BR> NIC considers this a private local matter that must be settled among <BR> <BR> <BR> <BR>Stahl [Page 2] <BR> <BR>RFC 1032 DOMAIN ADMINISTRATORS GUIDE November 1987 <BR> <BR> <BR> the parties involved prior to their commencing the registration <BR> process with the NIC. Therefore, it is assumed that the responsible <BR> person for a domain will have resolved any local conflicts among the <BR> members of his domain before registering that domain with the NIC. <BR> The NIC will give guidance, if requested, by answering specific <BR> technical questions, but will not provide arbitration in disputes at <BR> the local level. This policy is also in keeping with the distributed <BR> hierarchical nature of the domain-naming system in that it helps to <BR> distribute the tasks of solving problems and handling questions. <BR> <BR> Naming conventions for hosts should follow the rules specified in <BR> RFC-952. From a technical standpoint, domain names can be very long. <BR> Each segment of a domain name may contain up to 64 characters, but <BR> the NIC strongly advises DAs to choose names that are 12 characters <BR> or fewer, because behind every domain system there is a human being <BR>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -