We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

DNS Service – TLD Zone Sample Clauses

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.”)
DNS Service – TLD Zone. Contents 1.1. Apex SOA record 1.2. Apex NS records and in-­‐bailiwick glue for the TLD’s DNS servers 1.3. NS records and in-­‐bailiwick glue for DNS servers of registered names in the TLD
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
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. 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. 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...
DNS Service – TLD Zone. Contents Anti-Abuse Searchable Whois

Related to DNS Service – TLD Zone

  • DNS Service TLD Zone Contents 1.1. Apex SOA record 1.2. Apex NS records and in-­‐bailiwick glue for the TLD’s DNS servers 1.3. NS records and in-­‐bailiwick glue for DNS servers of registered names in the TLD

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

  • Service Term XOOM agrees to act as your exclusive natural gas supplier and will provide competitive retail natural gas service to you. The term of this Contract will begin when your local utility switches your account to XOOM and will continue on a month-to-month basis as set forth in the accompanying Product Sheet.

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

  • Service Terms Each Service Order will provide for a service term. At the end of the service term of any Service Order, unless either party gives written notice to the other party of its intention not to renew at least ninety (90) days before the end of a service term, the term of such Service Order will automatically renew for successive twelve (12) month periods. Termination of one Service Order will not affect the term of any other Service Order.

  • Network Services Local Access Services In lieu of any other rates and discounts, Customer will pay fixed monthly recurring local loop charges ranging from $1,200 to $2,000 for TDM-based DS-3 Network Services Local Access Services at 2 CLLI codes mutually agreed upon by Customer and Company.

  • Verizon OSS Services Access to Verizon Operations Support Systems functions. The term “Verizon OSS Services” includes, but is not limited to: (a) Verizon’s provision of ECI Usage Information to ECI pursuant to Section 8.3 of this Attachment; and, (b) “Verizon OSS Information”, as defined in Section 8.1.4 of this Attachment.

  • Availability of Verizon Telecommunications Services 3.1 Verizon will provide a Verizon Telecommunications Service to Reconex 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. 3.2 Except as otherwise required by Applicable Law, subject to Section 3.1, Verizon shall have the right to add, modify, grandfather, discontinue or withdraw, Verizon Telecommunications Services at any time, without the consent of Reconex. 3.3 To the extent required by Applicable Law, the Verizon Telecommunications Services to be provided to Reconex for resale pursuant to this Attachment will include a Verizon Telecommunications Service customer-specific contract service arrangement (“CSA”) (such as a customer specific pricing arrangement or individual case based pricing arrangement) that Verizon is providing to a Verizon Customer at the time the CSA is requested by Reconex.

  • ADS Services Up to U.S. $5.00 per 100 ADSs (or fraction thereof) held on the applicable record date(s) established by the Depositary. Person holding ADSs on the applicable record date(s) established by the Depositary.

  • Portion of Products/Services Available If only a portion of Products and/or Services is available for shipment or performance to meet the Delivery Date, Supplier shall promptly notify DXC and proceed unless otherwise directed by DXC. Supplier shall be responsible for any cost increase in the shipment of Products due to its failure to meet the Delivery Date and/or if such method does not comply with DXC’s shipping instructions.