Generic Top-Level Domain (gTLD) Registry Agreements
Proposed Unsponsored TLD Agreement: Appendix C, Section 3 (.biz)
C.3 Zone File generation, Distribution, and Publication NeuLevel will generate and propagate DNS zone file updates to the DNS server array incrementally as transactional updates initiated by the SRS resulting from new domain name registrations. Updates will be initiated from the SRS, and queued and propagated to the DNS server array in near real-time consistent with the applicable service level requirements. The NeuLevel registry would store only the following resource records in the zone file database:
NeuLevel will implement, on a reasonable schedule, glue-generation and pruning criteria specified by ICANN from time to time. Zone File Access Program NeuLevel will provide a data mart to enable registrars to access the zone file in bulk. Our proposed query program will:
Logging and Data Back-up All zone files and updates are generated using information from the SRS database. All updates are recorded as database transaction logs. Zone File-Generation Architecture Zone file information is stored in the SRS database (along with all other registry data) and replicated to a zone distribution server within defined service levels. See Appendix D, item 3.5.1. The database stored on the zone distribution server is in turn replicated out to a database at the nameserver data centers. Standards Compliance The DNS name server array will comply with the IETF standards for the DNS (RFC1035, RFC2181, RFC 2182). In addition, DNS extensions (security, transactional updates, internationalization, etc.) adopted or proposed by IETF will be assessed and supported consistent with industry acceptance and prudent operational considerations as part of the release requirements definition for the initial registry release and each subsequent one. NeuLevel expects to implement all applicable best-practice recommendations contained in RFC2870 (Root Nameserver Operational Requirements), as they become practicable. Comments concerning the layout, construction and functionality of this site should be sent to webmaster@icann.org. (c) 2001 The Internet Corporation for Assigned Names and Numbers. All rights reserved. |