DNS service availability Sample Clauses

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.
Sample 1Sample 2Sample 3See All (2k)
AutoNDA by SimpleDocs
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 name server availability. Refers to the ability of a public-DNS registered “IP address” of a particular name server listed as authoritative for a domain name, to answer DNS queries from an Internet user. All the public DNS-registered “IP address” of all name servers of the domain name being monitored shall be tested individually. If 51% or more of the DNS testing probes get undefined/unanswered results from “DNS tests” to a name server “IP address” during a given time, the name server “IP address” will be considered unavailable.
Sample 1Sample 2Sample 3See All (1k)
DNS service availability. Service availability as it applies to the DNS Service refers to the ability of the Nameservers, as a group, to resolve a DNS query from an Internet user. The committed Performance Specification is 99.999% measured in Monthly Timeframes. Performance Level. At any time at which it is available, each Nameserver (including a cluster of Nameservers addressed at a shared IP address) MUST be able to handle a load of queries for DNS data that is three times the measured daily peak (averaged over the Monthly Timeframe) of such requests on the most loaded Nameserver. Cross-Network Nameserver Performance Requirements. The committed Performance Specification for cross-network Nameserver performance is a measured Round-trip time of less than 300 ms and measured packet loss of fewer than 10%. Cross-network Nameserver performance measurements will be conducted by ICANN at times of it’s choosing, in the following manner: The measurements will be conducted by sending strings of DNS request packets from each of four measuring locations to each of the Nameservers and observing the responses from the Nameservers. (These strings of requests and responses are referred to as a "CNNP Test".) The measuring locations will be four root nameserver locations (on the US East Coast, US West Coast, Asia, and Europe). Each string of request packets will consist of 100 UDP packets at 10-second intervals requesting ns records for arbitrarily selected second-level domains in the Sponsored TLD, preselected to ensure that the names exist in the Sponsored TLD and are resolvable. The packet loss (i.e. the percentage of response packets not received) and the average Round-trip time for response packets received will be noted. To meet the packet loss and Round-trip-time requirements for a particular CNNP Test, all three of the following must be true: The Round-trip time and packet loss from each measurement location to at least one Nameserver must not exceed the required values. The Round-trip time to each of 75% of the Nameservers from at least one of the measurement locations must not exceed the required value. The packet loss to each of the Nameservers from at least one of the measurement locations must not exceed the required value. Any failing CNNP Test result obtained during an identified Core Internet Service Failure shall not be considered. To ensure a properly diverse testing sample, ICANN will conduct the CNNP Tests at varying times (i.e. at different times of day, as well as on differen...
Sample 1Sample 2Sample 3See All (14)
DNS service availability. DNS Service Availability refers to the ability of the group of listed-as-authoritative name servers of a particular registered 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
Sample 1Sample 2
DNS service availability. Service availability as it applies to the DNS Service refers to the ability of the Nameservers, as a group, to resolve a DNS query from an Internet user. The committed Performance Specification is 99.999% measured in Monthly Timeframes.
Sample 1
DNS service availability. DNS Service Availability Objective To manage and monitor the availability of the DNS Service for the .nz TLD. Definition Availability of the DNS Service requires ALL the following to be met: • 100% of internet users valid DNS requests received successfully query the delegation and glue of a domain in the .nz TLD; • the dissemination of .nz TLD zone files to the .nz zone servers; • A DNS server is available when it responds authoritively to valid queries within the required transaction response time using the current zone file when accessed outside the agreed zone push window time; • During the zone push window time all DNS servers should respond using either the current (new) or the immediately preceding (old) zone file. • At least 50% of the published DNS servers must be available at any one time. In the event that less than 50% of the published DNS servers are available then an exception report will be provided to the DNC. Target The DNS Service online availability is required to be 100% available at all times, including during planned outages. Calculation of DNS Service Availability • Percentage available = (Scheduled availability – Any outage time) / (scheduled availability) * 100. • Scheduled availability is the number of minutes in the calendar month period being measured. Calculation of DNS Server Availability • Percentage available = (Scheduled availability – Unscheduled Outage time) / (scheduled availability) * 100. • Scheduled availability is the number of minutes in the calendar month period being measured. • Unscheduled DNS server outage time is calculated for each DNS server by summing up the times of the individual DNS server outages that occurred during the period. Elapsed time of an outage is measured in minutes from the time the DNS server is unavailable (see availability definition above) until it is again available.
Sample 1
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 an Internet userDNS probes. For the service to be considered available at some point in timea particular moment, at least, two of the delegated name servers registered in the DNS must have defined successful results from “DNS tests” to each of their public-DNS registered “IP addresses“” to which the name server resolves over both (UDP and TCP) transports. If 51% or more of the DNS testing probes see the service as unavailable over any of the transports (UDP or TCP) during a given time, the DNS service will be considered unavailable.
Sample 1
AutoNDA by SimpleDocs

Related to DNS service availability

  • EPP service availability Refers to the ability of the TLD EPP servers as a group, to respond to commands from the Registry accredited Registrars, who already have credentials to the servers. The response shall include appropriate data from the Registry System. An EPP command with “EPP command RTT” 5 times higher than the corresponding SLR will be considered as unanswered. If 51% or more of the EPP testing probes see the EPP service as unavailable during a given time, the EPP service will be considered unavailable.

  • Service Availability You understand that Service availability is at all times conditioned upon the corresponding operation and availability of the communication systems used in communicating your instructions and requests to the Credit Union. We will not be liable or have any responsibility of any kind for any loss or damage thereby incurred by you in the event of any failure or interruption of such communication systems or services resulting from the act or omission of any third party, or from any other cause not reasonably within the control of the Credit Union.

  • RDDS availability Refers to the ability of all the RDDS services for the TLD, to respond to queries from an Internet user with appropriate data from the relevant Registry System. If 51% or more of the RDDS testing probes see any of the RDDS services as unavailable during a given time, the RDDS will be considered unavailable.

  • High Availability Registry Operator will conduct its operations using network and geographically diverse, redundant servers (including network-­‐level redundancy, end-­‐node level redundancy and the implementation of a load balancing scheme where applicable) to ensure continued operation in the case of technical failure (widespread or local), or an extraordinary occurrence or circumstance beyond the control of the Registry Operator. Registry Operator’s emergency operations department shall be available at all times to respond to extraordinary occurrences.

  • DNS name server availability Refers to the ability of a public-­‐DNS registered “IP address” of a particular name server listed as authoritative for a domain name, to answer DNS queries from an Internet user. All the public DNS-­‐registered “IP address” of all name servers of the domain name being monitored shall be tested individually. If 51% or more of the DNS testing probes get undefined/unanswered results from “DNS tests” to a name server “IP address” during a given time, the name server “IP address” will be considered unavailable.

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