📄 00000001.htm
字号:
<HTML><HEAD> <TITLE>BBS水木清华站∶精华区</TITLE></HEAD><BODY><CENTER><H1>BBS水木清华站∶精华区</H1></CENTER>Network Working Group M. Lottor <BR>Request For Comments: 1033 SRI International <BR> November 1987 <BR> <BR> <BR> DOMAIN ADMINISTRATORS OPERATIONS GUIDE <BR> <BR> <BR> <BR>STATUS OF THIS MEMO <BR> <BR> This RFC provides guidelines for domain administrators in operating a <BR> domain server and maintaining their portion of the hierarchical <BR> database. Familiarity with the domain system is assumed. <BR> Distribution of this memo is unlimited. <BR> <BR>ACKNOWLEDGMENTS <BR> <BR> This memo is a formatted collection of notes and excerpts from the <BR> references listed at the end of this document. Of particular mention <BR> are Paul Mockapetris and Kevin Dunlap. <BR> <BR>INTRODUCTION <BR> <BR> A domain server requires a few files to get started. It will <BR> normally have some number of boot/startup files (also known as the <BR> "safety belt" files). One section will contain a list of possible <BR> root servers that the server will use to find the up-to-date list of <BR> root servers. Another section will list the zone files to be loaded <BR> into the server for your local domain information. A zone file <BR> typically contains all the data for a particular domain. This guide <BR> describes the data formats that can be used in zone files and <BR> suggested parameters to use for certain fields. If you are <BR> attempting to do anything advanced or tricky, consult the appropriate <BR> domain RFC's for more details. <BR> <BR> Note: Each implementation of domain software may require different <BR> files. Zone files are standardized but some servers may require <BR> other startup files. See the appropriate documentation that comes <BR> with your software. See the appendix for some specific examples. <BR> <BR>ZONES <BR> <BR> A zone defines the contents of a contiguous section of the domain <BR> space, usually bounded by administrative boundaries. There will <BR> typically be a separate data file for each zone. The data contained <BR> in a zone file is composed of entries called Resource Records (RRs). <BR> <BR> <BR> <BR> <BR>Lottor [Page 1] <BR> <BR>RFC 1033 DOMAIN OPERATIONS GUIDE November 1987 <BR> <BR> <BR> You may only put data in your domain server that you are <BR> authoritative for. You must not add entries for domains other than <BR> your own (except for the special case of "glue records"). <BR> <BR> A domain server will probably read a file on start-up that lists the <BR> zones it should load into its database. The format of this file is <BR> not standardized and is different for most domain server <BR> implementations. For each zone it will normally contain the domain <BR> name of the zone and the file name that contains the data to load for <BR> the zone. <BR> <BR>ROOT SERVERS <BR> <BR> A resolver will need to find the root servers when it first starts. <BR> When the resolver boots, it will typically read a list of possible <BR> root servers from a file. <BR> <BR> The resolver will cycle through the list trying to contact each one. <BR> When it finds a root server, it will ask it for the current list of <BR> root servers. It will then discard the list of root servers it read <BR> from the data file and replace it with the current list it received. <BR> <BR> Root servers will not change very often. You can get the names of <BR> current root servers from the NIC. <BR> <BR> FTP the file NETINFO:ROOT-SERVERS.TXT or send a mail request to <BR> <A HREF="mailto:NIC@SRI-NIC.ARPA.">NIC@SRI-NIC.ARPA.</A> <BR> <BR> As of this date (June 1987) they are: <BR> <BR> SRI-NIC.ARPA 10.0.0.51 26.0.0.73 <BR> C.ISI.EDU 10.0.0.52 <BR> BRL-AOS.ARPA 192.5.25.82 192.5.22.82 128.20.1.2 <BR> A.ISI.EDU 26.3.0.103 <BR> <BR>RESOURCE RECORDS <BR> <BR> Records in the zone data files are called resource records (RRs). <BR> They are specified in RFC-883 and RFC-973. An RR has a standard <BR> format as shown: <BR> <BR> <name> [<ttl>] [<class>] <type> <data> <BR> <BR> The record is divided into fields which are separated by white space. <BR> <BR> <name> <BR> <BR> The name field defines what domain name applies to the given <BR> <BR> <BR> <BR>Lottor [Page 2] <BR> <BR>RFC 1033 DOMAIN OPERATIONS GUIDE November 1987 <BR> <BR> <BR> RR. In some cases the name field can be left blank and it will <BR> default to the name field of the previous RR. <BR> <BR> <ttl> <BR> <BR> TTL stands for Time To Live. It specifies how long a domain <BR> resolver should cache the RR before it throws it out and asks a <BR> domain server again. See the section on TTL's. If you leave <BR> the TTL field blank it will default to the minimum time <BR> specified in the SOA record (described later). <BR> <BR> <class> <BR> <BR> The class field specifies the protocol group. If left blank it <BR> will default to the last class specified. <BR> <BR> <type> <BR> <BR>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -