Common use of DNS Service – TLD Zone Contents 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: Apex SOA record Apex NS records and in-bailiwick glue for the TLD’s DNS servers NS records and in-bailiwick glue for DNS servers of registered names in the TLD DS records for registered names in the TLD 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. Anti-Abuse Registry Operator may suspend, delete or otherwise make changes to domain names in compliance with its anti-abuse policy. Internationalized Domain Names (IDNs) Registry Operator may offer registration of IDNs at the second and lower levels provided that Registry Operator complies with the following requirements: Registry Operator must offer Registrars support for handling IDN registrations in EPP. Registry Operator must handle variant IDNs as follows:

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: Apex SOA record Apex NS records and in-bailiwick glue for the TLD’s DNS servers NS records and in-bailiwick glue for DNS servers of registered names in the TLD DS records for registered names in the TLD 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. Searchable Whois Notwithstanding anything else in this Agreement, Registry Operator must offer a searchable Whois service compliant with the requirements described in Section 1.10 of Specification 4 of this Agreement. Registry Operator must make available the services only to authenticated users after they logged in by supplying proper credentials (e.g., user name and password). Registry Operator must issue such credentials exclusively to eligible users and institutions that supply sufficient proof of their legitimate interest in this feature (e.g., law enforcement agencies). Domain data change notifications Registry Operator may offer the Registration Data Change Notifications service, which is a Registry Service that allows the registrant and the administrative contact of the domain name to promptly receive notifications when the registration data of a domain name is changed. Anti-Abuse Registry Operator may suspend, delete or otherwise make changes to domain names in compliance with its anti-abuse policy. Internationalized Domain Names (IDNs) Registry Operator may offer registration of IDNs at the second and lower levels provided that Registry Operator complies with the following requirements: Registry Operator must offer Registrars support for handling IDN registrations in EPP. Registry Operator must handle variant IDNs as follows:: By default variant IDNs (as defined in the Registry Operator’s IDN tables and IDN Registration Rules) must be blocked from registration. Variant IDNs may be activated when requested by the sponsoring Registrar of the canonical name as described in the IDN Tables and IDN Registration Rules. Active variant IDNs must be provisioned in the TLD’s DNS zone file as zone cuts using the same NS resource records as the canonical name. Registry Operator may offer registration of IDNs in the following languages/scripts (IDN Tables and IDN Registration Rules will be published by the Registry Operator as specified in the ICANN IDN Implementation Guidelines): German language CONSENSUS POLICIES AND TEMPORARY POLICIES SPECIFICATION Consensus Policies.