📄 00000001.htm
字号:
incremented anytime a change is made to data in the zone. <BR> <BR> <BR> <BR> <BR>Lottor [Page 5] <BR> <BR>RFC 1033 DOMAIN OPERATIONS GUIDE November 1987 <BR> <BR> <BR> <refresh> is how long, in seconds, a secondary name server is to <BR> check with the primary name server to see if an update is needed. A <BR> good value here would be one hour (3600). <BR> <BR> <retry> is how long, in seconds, a secondary name server is to retry <BR> after a failure to check for a refresh. A good value here would be <BR> 10 minutes (600). <BR> <BR> <expire> is the upper limit, in seconds, that a secondary name server <BR> is to use the data before it expires for lack of getting a refresh. <BR> You want this to be rather large, and a nice value is 3600000, about <BR> 42 days. <BR> <BR> <minimum> is the minimum number of seconds to be used for TTL values <BR> in RRs. A minimum of at least a day is a good value here (86400). <BR> <BR> There should only be one SOA record per zone. A sample SOA record <BR> would look something like: <BR> <BR> @ IN SOA SRI-NIC.ARPA. HOSTMASTER.SRI-NIC.ARPA. ( <BR> 45 ;serial <BR> 3600 ;refresh <BR> 600 ;retry <BR> 3600000 ;expire <BR> 86400 ) ;minimum <BR> <BR> <BR>NS (Name Server) <BR> <BR> <domain> [<ttl>] [<class>] NS <server> <BR> <BR> The NS record lists the name of a machine that provides domain <BR> service for a particular domain. The name associated with the RR is <BR> the domain name and the data portion is the name of a host that <BR> provides the service. If machines SRI-NIC.ARPA and C.ISI.EDU provide <BR> name lookup service for the domain COM then the following entries <BR> would be used: <BR> <BR> COM. NS SRI-NIC.ARPA. <BR> NS C.ISI.EDU. <BR> <BR> Note that the machines providing name service do not have to live in <BR> the named domain. There should be one NS record for each server for <BR> a domain. Also note that the name "COM" defaults for the second NS <BR> record. <BR> <BR> NS records for a domain exist in both the zone that delegates the <BR> domain, and in the domain itself. <BR> <BR> <BR> <BR>Lottor [Page 6] <BR> <BR>RFC 1033 DOMAIN OPERATIONS GUIDE November 1987 <BR> <BR> <BR>GLUE RECORDS <BR> <BR> If the name server host for a particular domain is itself inside the <BR> domain, then a 'glue' record will be needed. A glue record is an A <BR> (address) RR that specifies the address of the server. Glue records <BR> are only needed in the server delegating the domain, not in the <BR> domain itself. If for example the name server for domain SRI.COM was <BR> KL.SRI.COM, then the NS record would look like this, but you will <BR> also need to have the following A record. <BR> <BR> SRI.COM. NS KL.SRI.COM. <BR> KL.SRI.COM. A 10.1.0.2 <BR> <BR> <BR>A (Address) <BR> <BR> <host> [<ttl>] [<class>] A <address> <BR> <BR> The data for an A record is an internet address in dotted decimal <BR> form. A sample A record might look like: <BR> <BR> SRI-NIC.ARPA. A 10.0.0.51 <BR> <BR> There should be one A record for each address of a host. <BR> <BR>CNAME ( Canonical Name) <BR> <BR> <nickname> [<ttl>] [<class>] CNAME <host> <BR> <BR> The CNAME record is used for nicknames. The name associated with the <BR> RR is the nickname. The data portion is the official name. For <BR> example, a machine named SRI-NIC.ARPA may want to have the nickname <BR> NIC.ARPA. In that case, the following RR would be used: <BR> <BR> NIC.ARPA. CNAME SRI-NIC.ARPA. <BR> <BR> There must not be any other RRs associated with a nickname of the <BR> same class. <BR> <BR> Nicknames are also useful when a host changes it's name. In that <BR> case, it is usually a good idea to have a CNAME pointer so that <BR> people still using the old name will get to the right place. <BR> <BR> <BR> <BR> <BR> <BR> <BR> <BR> <BR> <BR>Lottor [Page 7] <BR> <BR>RFC 1033 DOMAIN OPERATIONS GUIDE November 1987 <BR> <BR> <BR>HINFO (Host Info) <BR> <BR> <host> [<ttl>] [<class>] HINFO <hardware> <software> <BR> <BR> The HINFO record gives information about a particular host. The data <BR> is two strings separated by whitespace. The first string is a <BR> hardware description and the second is software. The hardware is <BR> usually a manufacturer name followed by a dash and model designation. <BR> The software string is usually the name of the operating system. <BR> <BR> Official HINFO types can be found in the latest Assigned Numbers RFC, <BR> the latest of which is RFC-1010. The Hardware type is called the <BR> Machine name and the Software type is called the System name. <BR> <BR> Some sample HINFO records: <BR> <BR> SRI-NIC.ARPA. HINFO DEC-2060 TOPS20 <BR> UCBARPA.Berkeley.EDU. HINFO VAX-11/780 UNIX <BR>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -