Common use of DNS Service Clause in Contracts

DNS Service. TLD Zone Contents 1.1. For the “Internet” (IN) Class: 1.1.1. Apex SOA record 1.1.2. Apex NS records and in-bailiwick glue for the TLD’s DNS servers 1.1.3. NS records and in-bailiwick glue for DNS servers of registered names in the TLD 1.1.4. DS records for registered names in the TLD 1.1.5. Records associated with signing the TLD zone (e.g., RRSIG, DNSKEY, NSEC, NSEC3PARAM and NSEC3) 1.1.6. Apex TXT record for zone versioning purposes 1.1.7. Apex TYPE65534 record for automatic dnssec signing signaling 1.2. For the “Chaos” (CH) Class: 1.2.1. TXT records for server version/identification (e.g., TXT records for “version.bind.”, “id.server.”, “authors.bind” and/or “hostname.bind.”) (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 or class into its TLD DNS service (other than those listed in Sections 1.1 or 1.2 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 and/or classes 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 1.1. For the “Internet” (IN) Class: 1.1.1. Apex SOA record 1.1.2. Apex NS records and in-bailiwick glue for the TLD’s DNS servers 1.1.3. NS records and in-bailiwick glue for DNS servers of registered names in the TLD 1.1.4. DS records for registered names in the TLD 1.1.5. Records associated with signing the TLD zone (e.g., RRSIG, DNSKEY, NSEC, NSEC3PARAM and NSEC3) 1.1.6. Apex TXT record for zone versioning purposes 1.1.7. Apex TYPE65534 record for automatic dnssec signing signaling 1.2. For the “Chaos” (CH) Class: 1.2.1. TXT records for server version/identification (e.g., TXT records for “version.bind.”, “id.server.”, “authors.bind” and/or “hostname.bind.”) (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 or class into its TLD DNS service (other than those listed in Sections 1.1 or 1.2 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 and/or classes in the TLD zone, even if approved, might not work as intended for all users due to lack of software support. Consensus Policies.

DNS Service. TLD Zone Contents 1.1. For the “Internet” (IN) Class: 1.1.1. Apex SOA record 1.1.2. Apex NS records and in-bailiwick glue for the TLD’s DNS servers 1.1.3. NS records and in-bailiwick glue for DNS servers of registered names in the TLD 1.1.4. DS records for registered names in the TLD 1.1.5. Records associated with signing the TLD zone (e.g., RRSIG, DNSKEY, NSEC, NSEC3PARAM and NSEC3) 1.1.6. Apex TXT record for zone versioning purposes 1.1.7. Apex TYPE65534 record for automatic dnssec signing signalingsigningsignaling 1.2. For the “Chaos” (CH) Class: 1.2.1. TXT records for server version/identification (e.g., TXT records for “version.bind.”, “id.server.”, “authors.bind” and/or “hostname.bind.”) (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 or class into its TLD DNS service (other than those listed in Sections 1.1 or 1.2 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 and/or classes in the TLD zone, even if approved, might not work as intended for all users due to lack of software support.