DNS Service – TLD Zone Contents Sample Clauses

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:
AutoNDA by SimpleDocs
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. 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). Registry Operator shall use rate-limiting to prevent abuse of the searchable Whois service. CONSENSUS POLICIES AND TEMPORARY POLICIES SPECIFICATION Consensus Policies.
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 DNS service are: For the “Internet” (IN) Class: 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 (e.g., RRSIG, DNSKEY, NSEC, NSEC3PARAM and NSEC3) Apex TXT record for zone versioning purposes Apex TYPE65534 record for automatic dnssec signing signaling For the “Chaos” (CH) Class: TXT records for server version/identification (e.g., TXT records for “version.bind.”, “id.server.”, “authors.bind” and/or “hostname.bind.”)
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: Regi...

Related to DNS Service – TLD Zone Contents

  • DNS service availability Refers to the ability of the group of listed-­‐as-­‐authoritative name servers of a particular domain name (e.g., a TLD), to answer DNS queries from DNS probes. For the service to be considered available at a particular moment, at least, two of the delegated name servers registered in the DNS must have successful results from “DNS tests” to each of their public-­‐DNS registered “IP addresses” to which the name server resolves. If 51% or more of the DNS testing probes see the service as unavailable during a given time, the DNS service will be considered unavailable.

  • 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:

  • Service Content SORACOM Air Global Service contains the following services. Subscription (plan) Content plan01s It is suitable for IoT/M2M equipment. plan01s - Low Data Volume It is suitable for IoT/M2M equipment. Especially, it is suitable for small data usage. plan01 plan01 can be purchased in the USA and Japan. It is characterized by a wide coverage area. plan01 - Low Data Volume plan01 - Low Data Volume can be purchased in the USA and Japan. It is suitable for small data usage. plan02 plan02 can be purchased in Europe. Data communication charges are kept low in Europe and it is suitable for use in Europe. Subscription (Speed Class) Content s1 class Data Transmission Service that adjusts the outgoing and incoming transmission speed between the terminal and SORACOM so that the transmission is symmetrical

  • Availability of Verizon Telecommunications Services 3.1 Verizon will provide a Verizon Telecommunications Service to PNG for resale pursuant to this Attachment where and to the same extent, but only where and to the same extent that such Verizon Telecommunications Service is provided to Verizon’s Customers.

  • Verizon Retail Telecommunications Service Any Telecommunications Service that Verizon provides at retail to subscribers that are not Telecommunications Carriers. The term “Verizon Retail Telecommunications Service” does not include any Exchange Access service (as defined in Section 3(16) of the Act, 47 U.S.C. § 153(16)) provided by Verizon.

  • Your Guide to Selecting a Primary Care Provider (PCP) and Other Providers Quality healthcare begins with a partnership between you and your primary care provider (PCP). When you need care, call your PCP, who will help coordinate your care. Your healthcare coverage under this plan is provided or arranged through our network of PCPs, specialists, and other providers. You’re encouraged to: • become involved in your healthcare by asking providers about all treatment plans available and their costs; • take advantage of the preventive health services offered under this plan to help you stay healthy and find problems before they become serious. Each member is required to provide the name of his or her PCP. However, if the name of a PCP is not provided with the application, your enrollment will not be delayed and your coverage will not be cancelled. How to Find a PCP or Other Providers Finding a PCP in our network is easy. To select a provider, or to check that a provider is in our network, please use the “Find a Doctor” tool on our website or call Customer Service. Please note: We are not obligated to provide you with a provider. We are not liable for anything your provider does or does not do. We are not a healthcare provider and do not practice medicine, dentistry, furnish health care, or make medical judgments.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!