Common use of DNS Service Clause in Contracts

DNS Service. TLD Zone Contents Notwithstanding anything else in this Agreement, as indicated in section 2.2.3.3 of the gTLD Applicant Guidebook, permissible contents for the TLD’s zone are: 1. Apex SOA record 2. Apex NS records and in-­‐bailiwick glue for the TLD’s DNS servers 3. NS records and in-­‐bailiwick glue for DNS servers of registered names in the TLD 4. DS records for registered names in the TLD 5. Records associated with signing the TLD zone (i.e., RRSIG, DNSKEY, NSEC, and NSEC3) (Note: The above language effectively does not allow, among other things, the inclusion of DNS resource records that would enable a dotless domain name (e.g., apex A, AAAA, MX records) in the TLD zone.) If Registry Operator wishes to place any DNS resource record type into its TLD DNS zone (other than those listed in Sections 1.1 through 1.5 above), it must describe in detail its proposal and submit a Registry Services Evaluation Process (RSEP) request. This will be evaluated per RSEP to determine whether the service would create a risk of a meaningful adverse impact on security or stability of the DNS. Registry Operator recognizes and acknowledges that a service based on the use of less-­‐common DNS resource records in the TLD zone, even if approved, might not work as intended for all users due to lack of software support.

DNS Service. TLD Zone Contents Notwithstanding anything else in this Agreement, as indicated in section 2.2.3.3 of the gTLD Applicant Guidebook, permissible contents for the TLD’s zone are: 11.1. Apex SOA record 21.2. Apex NS records and in-­‐bailiwick in‐bailiwick glue for the TLD’s DNS servers 31.3. NS records and in-­‐bailiwick in‐bailiwick glue for DNS servers of registered names in the TLD 41.4. DS records for registered names in the TLD 51.5. Records associated with signing the TLD zone (i.e., RRSIG, DNSKEY, NSEC, and NSEC3) (Note: The above language effectively does not allow, among other things, the inclusion of DNS resource records that would enable a dotless domain name (e.g., apex A, AAAA, MX records) in the TLD zone.) If Registry Operator wishes to place any DNS resource record type into its TLD DNS zone (other than those listed in Sections 1.1 through 1.5 above), it must describe in detail its proposal and submit a Registry Services Evaluation Process (RSEP) request. This will be evaluated per RSEP to determine whether the service would create a risk of a meaningful adverse impact on security or stability of the DNS. Registry Operator recognizes and acknowledges that a service based on the use of less-­‐common less‐common DNS resource records in the TLD zone, even if approved, might not work as intended for all users due to lack of software support.