Default Managed DNS Sample Clauses

Default Managed DNS. Authoritative managed DNS hosting that does not allow for zone changes; however, this service satisfies all registry requirements. This infrastructure does not provide for any network redundancy or optimization of DNS resolution, and is only appropriate for defensive registrations for which resolution and performance are not deemed critical. There is no Service Level Agreement for this service. Exhibit 2 Service Level Agreement for Premium DNS Services (only) This Exhibit 2 is subject to the terms of and is hereby incorporated by reference to Schedule B of the Agreement. The terms of this Exhibit 2 are applicable only to the Premium DNS services, as defined in Schedule B, and with regard to those Premium DNS services, shall control if there is a conflict with the terms of this Schedule B.
Sample 1
AutoNDA by SimpleDocs

Related to Default Managed DNS

  • Developer Default Each of the following shall be an Event of Default by Developer:

  • Customer Default The occurrence at any time of any of the following events shall constitute a “Customer Default”:

  • Default Authorized User a. Breach by Authorized User An Authorized User’s breach shall not be deemed a breach of the Centralized Contract; rather, it shall be deemed a breach of the Authorized User’s performance under the terms and conditions of the Centralized Contract.

  • Termination for Concessionaire Default 37.1.1 Save as otherwise provided in this Agreement, in the event that any of the defaults specified below shall have occurred, and the Concessionaire fails to cure the default within the Cure Period set forth below, or where no Cure Period is specified, then within a Cure Period of 60 (sixty) days, the Concessionaire shall be deemed to be in default of this Agreement (the “Concessionaire Default”), unless the default has occurred solely as a result of any breach of this Agreement by the Authority or due to Force Majeure. The defaults referred to herein shall include:

  • Owner Default Failure of the Owner, which has not been remedied or waived, to pay the Contractor as required under the Construction Contract or to perform and complete or comply with the other material terms of the Construction Contract.

  • Developer Event of Default Any of the following events shall constitute an event of default by the Developer ("Developer Event of Default") unless such event has occurred as a result of a Force Majeure Event or the Authority Event of Default or any governmental action for reasons other than any breach, default or lapse on the part of the Developer:

  • Default and Consequences of Default 18.1 Interest on overdue invoices shall accrue daily from the date when payment becomes due, until the date of payment, at a rate of two and a half percent (2.5%) per calendar month (and at the Supplier’s sole discretion such interest shall compound monthly at such a rate) after as well as before any judgment.

  • Xxxxxx of Default Any one or more of the following shall constitute an “Event of Default” hereunder:

  • Termination for Default The County may, by written notice to the Contractor terminate this contract for default in whole or in part (delivery orders, if applicable) if the Contractor fails to:

  • H DEFAULT, DISRUPTION AND TERMINATION H1 Termination on insolvency and change of control H1.1 The Client may terminate the Contract with immediate effect by notice in writing where the Contractor is a company and in respect of the Contractor:

Time is Money Join Law Insider Premium to draft better contracts faster.