📄 00000003.htm
字号:
who must keep track of the names, addresses, contacts, and other data <BR> in a database. The longer the name, the more likely the data <BR> maintainer is to make a mistake. Users also will appreciate shorter <BR> names. Most people agree that short names are easier to remember and <BR> type; most domain names registered so far are 12 characters or fewer. <BR> <BR> Domain name assignments are made on a first-come-first-served basis. <BR> The NIC has chosen not to register individual hosts directly under <BR> the top-level domains it administers. One advantage of the domain <BR> naming system is that administration and data maintenance can be <BR> delegated down a hierarchical tree. Registration of hosts at the <BR> same level in the tree as a second-level domain would dilute the <BR> usefulness of this feature. In addition, the administrator of a <BR> domain is responsible for the actions of hosts within his domain. We <BR> would not want to find ourselves in the awkward position of policing <BR> the actions of individual hosts. Rather, the subdomains registered <BR> under these top-level domains retain the responsibility for this <BR> function. <BR> <BR> Countries that wish to be registered as top-level domains are <BR> required to name themselves after the two-letter country code listed <BR> in the international standard ISO-3166. In some cases, however, the <BR> two-letter ISO country code is identical to a state code used by the <BR> U.S. Postal Service. Requests made by countries to use the three- <BR> letter form of country code specified in the ISO-3166 standard will <BR> be considered in such cases so as to prevent possible conflicts and <BR> confusion. <BR> <BR> <BR> <BR> <BR> <BR> <BR> <BR> <BR> <BR>Stahl [Page 3] <BR> <BR>RFC 1032 DOMAIN ADMINISTRATORS GUIDE November 1987 <BR> <BR> <BR>HOW TO REGISTER <BR> <BR> Obtain a domain questionnaire from the NIC hostmaster, or FTP the <BR> file NETINFO:DOMAIN-TEMPLATE.TXT from host SRI-NIC.ARPA. <BR> <BR> Fill out the questionnaire completely. Return it via electronic mail <BR> to <A HREF="mailto:HOSTMASTER@SRI-NIC.ARPA.">HOSTMASTER@SRI-NIC.ARPA.</A> <BR> <BR> The APPENDIX to this memo contains the application form for <BR> registering a top-level or second-level domain with the NIC. It <BR> supersedes the version of the questionnaire found in RFC-920. The <BR> application should be submitted by the person administratively <BR> responsible for the domain, and must be filled out completely before <BR> the NIC will authorize establishment of a top-level or second-level <BR> domain. The DA is responsible for keeping his domain's data current <BR> with the NIC or with the registration agent with which his domain is <BR> registered. For example, the CSNET and UUCP managements act as <BR> domain filters, processing domain applications for their own <BR> organizations. They pass pertinent information along periodically to <BR> the NIC for incorporation into the domain database and root server <BR> files. The online file NETINFO:ALTERNATE-DOMAIN-PROCEDURE.TXT <BR> outlines this procedure. It is highly recommended that the DA review <BR> this information periodically and provide any corrections or <BR> additions. Corrections should be submitted via electronic mail. <BR> <BR>WHICH DOMAIN NAME? <BR> <BR> The designers of the domain-naming system initiated several general <BR> categories of names as top-level domain names, so that each could <BR> accommodate a variety of organizations. The current top-level <BR> domains registered with the DDN Network Information Center are ARPA, <BR> COM, EDU, GOV, MIL, NET, and ORG, plus a number of top-level country <BR> domains. To join one of these, a DA needs to be aware of the purpose <BR> for which it was intended. <BR> <BR> "ARPA" is a temporary domain. It is by default appended to the <BR> names of hosts that have not yet joined a domain. When the system <BR> was begun in 1984, the names of all hosts in the Official DoD <BR> Internet Host Table maintained by the NIC were changed by adding <BR> of the label ".ARPA" in order to accelerate a transition to the <BR> domain-naming system. Another reason for the blanket name changes <BR> was to force hosts to become accustomed to using the new style <BR> names and to modify their network software, if necessary. This <BR> was done on a network-wide basis and was directed by DCA in DDN <BR> Management Bulletin No. 22. Hosts that fall into this domain will <BR> eventually move to other branches of the domain tree. <BR> <BR> <BR> <BR> <BR> <BR>Stahl [Page 4] <BR> <BR>RFC 1032 DOMAIN ADMINISTRATORS GUIDE November 1987 <BR> <BR> <BR> "COM" is meant to incorporate subdomains of companies and <BR> businesses. <BR> <BR> "EDU" was initiated to accommodate subdomains set up by <BR> universities and other educational institutions. <BR> <BR> "GOV" exists to act as parent domain for subdomains set up by <BR> government agencies. <BR> <BR> "MIL" was initiated to act as parent to subdomains that are <BR> developed by military organizations. <BR> <BR> "NET" was introduced as a parent domain for various network-type <BR> organizations. Organizations that belong within this top-level <BR> domain are generic or network-specific, such as network service <BR> centers and consortia. "NET" also encompasses network <BR> management-related organizations, such as information centers and <BR> operations centers. <BR> <BR> "ORG" exists as a parent to subdomains that do not clearly fall <BR> within the other top-level domains. This may include technical- <BR> support groups, professional societies, or similar organizations. <BR> <BR> One of the guidelines in effect in the domain-naming system is that a <BR> host should have only one name regardless of what networks it is <BR> connected to. This implies, that, in general, domain names should <BR> not include routing information or addresses. For example, a host <BR> that has one network connection to the Internet and another to BITNET <BR> should use the same name when talking to either network. For a <BR> description of the syntax of domain names, please refer to Section 3 <BR> of RFC-1034. <BR> <BR>VERIFICATION OF DATA <BR> <BR> The verification process can be accomplished in several ways. One of <BR> these is through the NIC WHOIS server. If he has access to WHOIS, <BR> the DA can type the command "whois domain <domain name><return>". <BR> The reply from WHOIS will supply the following: the name and address <BR> of the organization "owning" the domain; the name of the domain; its <BR> administrative, technical, and zone contacts; the host names and <BR>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -