📄 00000002.htm
字号:
be able to register a domain name for a whole university. The naming <BR> authority can impose certain extra rules as long as they don't <BR> violate or conflict with the rights and interest of the registrars of <BR> subdomains; a top level domain registrar may e.g., require that there <BR> <BR> <BR> <BR>Beertema [Page 7] <BR> <BR>RFC 1537 Common DNS Data File Configuration Errors October 1993 <BR> <BR> <BR> be primary subdomain "ac" and "co" only and that subdomains be <BR> registered under those primary subdomains. <BR> <BR> The naming authority can also interfere in exceptional cases like the <BR> one mentioned in point 4, e.g., by temporarily removing a domain's <BR> entry from the nameserver zone files; this of course should be done <BR> only with extreme care and only as a last resort. <BR> <BR> When adding NS records for subdomains, top level domain nameserver <BR> managers should realize that the people setting up the nameserver for <BR> a subdomain often are rather inexperienced and can make mistakes that <BR> can easily lead to the subdomain becoming completely unreachable or <BR> that can cause unnecessary DNS traffic (see point 1). It is therefore <BR> highly recommended that, prior to entering such an NS record, the <BR> (top level) nameserver manager does a couple of sanity checks on the <BR> new nameserver (SOA record and timers OK?, MX records present where <BR> needed? No obvious errors made? Listed secondary servers <BR> operational?). Things that cannot be caught though by such checks <BR> are: <BR> <BR> - resolvers set up to use external hosts as nameservers <BR> <BR> - nameservers set up to use external hosts as forwarders <BR> without permission from those hosts. <BR> <BR> Care should also be taken when registering 2-letter subdomains. <BR> Although this is allowed, an implication is that abbreviated <BR> addressing (see STD 11, RFC 822, paragraph 6.2.2) is not possible in <BR> and under that subdomain. When requested to register such a domain, <BR> one should always notify the people of this consequence. As an <BR> example take the name "cs", which is commonly used for Computer <BR> Science departments: it is also the name of the top level domain for <BR> Czecho-Slovakia, so within the domain cs.foo.bar the <A HREF="mailto:user@host.cs">user@host.cs</A> is <BR> ambiguous in that in can denote both a user on the host <BR> host.cs.foo.bar and a user on the host "host" in Czecho-Slovakia. <BR> (This example does not take into account the recent political changes <BR> in the mentioned country). <BR> <BR>References <BR> <BR> [1] Mockapetris, P., "Domain Names Concepts and Facilities", STD 13, <BR> RFC 1034, USC/Information Sciences Institute, November 1987. <BR> <BR> [2] Mockapetris, P., "Domain Names Implementation and Specification", <BR> STD 13, RFC 1035, USC/Information Sciences Institute, November <BR> 1987. <BR> <BR> <BR> <BR> <BR> <BR>Beertema [Page 8] <BR> <BR>RFC 1537 Common DNS Data File Configuration Errors October 1993 <BR> <BR> <BR> [3] Partridge, C., "Mail Routing and the Domain System", STD 14, RFC <BR> 974, CSNET CIC BBN, January 1986. <BR> <BR> [4] Gavron, E., "A Security Problem and Proposed Correction With <BR> Widely Deployed DNS Software", RFC 1535, ACES Research Inc., <BR> October 1993. <BR> <BR> [5] Kumar, A., Postel, J., Neuman, C., Danzig, P., and S. Miller, <BR> "Common DNS Implementation Errors and Suggested Fixes", RFC 1536, <BR> USC/Information Sciences Institute, USC, October 1993. <BR> <BR>Security Considerations <BR> <BR> Security issues are not discussed in this memo. <BR> <BR>Author's Address <BR> <BR> Piet Beertema <BR> CWI <BR> Kruislaan 413 <BR> NL-1098 SJ Amsterdam <BR> The Netherlands <BR> <BR> Phone: +31 20 592 4112 <BR> FAX: +31 20 592 4199 <BR> EMail: <A HREF="mailto:Piet.Beertema@cwi.nl">Piet.Beertema@cwi.nl</A> <BR> <BR> <BR>Editor's Address <BR> <BR> Anant Kumar <BR> USC Information Sciences Institute <BR> 4676 Admiralty Way <BR> Marina Del Rey CA 90292-6695 <BR> <BR> Phone:(310) 822-1511 <BR> FAX: (310) 823-6741 <BR> EMail: <A HREF="mailto:anant@isi.edu">anant@isi.edu</A> <BR> <BR> <BR> <BR> <BR> <BR> <BR> <BR> <BR> <BR> <BR> <BR> <BR> <BR>Beertema [Page 9] <BR> <BR><CENTER><H1>BBS水木清华站∶精华区</H1></CENTER></BODY></HTML>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -