Dedicated to preserving the central
coordinating functions of the global
Format and Technical Requirements for Requests to Change TLD Nameservers in the Root Zone
Internet Assigned Numbers Authority
(This document applies only to TLDs as to which a written agreement is in effect between ICANN and the TLD delegee, sponsor, or operator.)
3. Nameserver change requests are subject to verification of authenticity and authorization. Both the listed technical contact and the listed administrative contact should be available to verify that the request is authentic and they authorize the requested change. Except where a written agreement between ICANN and the TLD delegee, sponsor, or operator expressly states to the contrary, the IANA shall be entitled to rely on authorization of either the administrative or technical contact as constituting a request for nameserver change by the TLD delegee, sponsor, or operator.
4. Requests for changes to nameservice for ccTLDs (i.e. TLDs having two-letter labels) must result in delegation to at least two nameservers, preferably on different network segments. Requests for changes to nameservice for other TLDs must result in delegation to nameservers on at least five different network segments.
6. Prior to submitting the request, nameservice should be set up at all the nameservers to which delegation is to be made. Lame delegations (i.e. delegations to servers without operating nameservice for the delegated zone) will not ordinarily be made.
7. The IANA must have zone file access. Except where other arrangements are made (such as for TLDs with large zones), this means that zone file transfers must be enabled at all nameservers for transfers to at least 126.96.36.199/16 and 188.8.131.52/20.
(9 May 2001)
Please send comments on this web site to: email@example.com
Page Updated 29-Mar-2002
©2002 The Internet Assigned Numbers Authority All rights reserved.