📄 00000003.htm
字号:
Title President <BR> Mail Address The NetWorthy Corporation <BR> 4676 Andrews Way, Suite 100 <BR> Santa Clara, CA 94302-1212 <BR> Phone Number (415) 123-4567 <BR> Net Mailbox <A HREF="mailto:Sassafrass@ECHO.TNC.COM">Sassafrass@ECHO.TNC.COM</A> <BR> NIC Handle PQS <BR> <BR> (3) The NIC handle of the technical contact for the domain. <BR> Alternately, the person's name, title, mailing address, phone number, <BR> organization, and network mailbox. This is the contact point for <BR> problems concerning the domain or zone, as well as for updating <BR> information about the domain or zone. <BR> <BR> <BR> <BR> <BR>Stahl [Page 10] <BR> <BR>RFC 1032 DOMAIN ADMINISTRATORS GUIDE November 1987 <BR> <BR> <BR> For example: <BR> <BR> Technical and Zone Contact <BR> <BR> Organization The NetWorthy Corporation <BR> Name Ansel A. Aardvark <BR> Title Executive Director <BR> Mail Address The NetWorthy Corporation <BR> 4676 Andrews Way, Suite 100 <BR> Santa Clara, CA. 94302-1212 <BR> Phone Number (415) 123-6789 <BR> Net Mailbox <A HREF="mailto:Aardvark@ECHO.TNC.COM">Aardvark@ECHO.TNC.COM</A> <BR> NIC Handle AAA2 <BR> <BR> (4) The name of the domain (up to 12 characters). This is the name <BR> that will be used in tables and lists associating the domain with the <BR> domain server addresses. [While, from a technical standpoint, domain <BR> names can be quite long (programmers beware), shorter names are <BR> easier for people to cope with.] <BR> <BR> For example: TNC <BR> <BR> (5) A description of the servers that provide the domain service for <BR> translating names to addresses for hosts in this domain, and the date <BR> they will be operational. <BR> <BR> A good way to answer this question is to say "Our server is <BR> supplied by person or company X and does whatever their standard <BR> issue server does." <BR> <BR> For example: Our server is a copy of the one operated by <BR> the NIC; it will be installed and made operational on <BR> 1 November 1987. <BR> <BR> (6) Domains must provide at least two independent servers for the <BR> domain. Establishing the servers in physically separate locations <BR> and on different PSNs is strongly recommended. A description of the <BR> server machine and its backup, including <BR> <BR> <BR> <BR> <BR> <BR> <BR> <BR> <BR> <BR> <BR> <BR> <BR> <BR>Stahl [Page 11] <BR> <BR>RFC 1032 DOMAIN ADMINISTRATORS GUIDE November 1987 <BR> <BR> <BR> (a) Hardware and software (using keywords from the Assigned <BR> Numbers RFC). <BR> <BR> (b) Host domain name and network addresses (which host on which <BR> network for each connected network). <BR> <BR> (c) Any domain-style nicknames (please limit your domain-style <BR> nickname request to one) <BR> <BR> For example: <BR> <BR> - Hardware and software <BR> <BR> VAX-11/750 and UNIX, or <BR> IBM-PC and MS-DOS, or <BR> DEC-1090 and TOPS-20 <BR> <BR> - Host domain names and network addresses <BR> <BR> BAR.FOO.COM 10.9.0.193 on ARPANET <BR> <BR> - Domain-style nickname <BR> <BR> BR.FOO.COM (same as BAR.FOO.COM 10.9.0.13 on ARPANET) <BR> <BR> (7) Planned mapping of names of any other network hosts, other than <BR> the server machines, into the new domain's naming space. <BR> <BR> For example: <BR> <BR> BAR-FOO2.ARPA (10.8.0.193) -> FOO2.BAR.COM <BR> BAR-FOO3.ARPA (10.7.0.193) -> FOO3.BAR.COM <BR> BAR-FOO4.ARPA (10.6.0.193) -> FOO4.BAR.COM <BR> <BR> <BR> (8) An estimate of the number of hosts that will be in the domain. <BR> <BR> (a) Initially <BR> (b) Within one year <BR> (c) Two years <BR> (d) Five years. <BR> <BR> For example: <BR> <BR> (a) Initially = 50 <BR> (b) One year = 100 <BR> (c) Two years = 200 <BR> (d) Five years = 500 <BR> <BR> <BR> <BR>Stahl [Page 12] <BR> <BR>RFC 1032 DOMAIN ADMINISTRATORS GUIDE November 1987 <BR> <BR> <BR> (9) The date you expect the fully qualified domain name to become <BR> the official host nam
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -