Information Session DNS Service level recommendations and experiences.

Slides:



Advertisements
Similar presentations
SERVICE LEVEL AGREEMENTS The Technical Contract Within the Master Agreement.
Advertisements

1 Dynamic DNS. 2 Module - Dynamic DNS ♦ Overview The domain names and IP addresses of hosts and the devices may change for many reasons. This module focuses.
SQL Server Disaster Recovery Chris Shaw Sr. SQL Server DBA, Xtivia Inc.
11 TROUBLESHOOTING Chapter 12. Chapter 12: TROUBLESHOOTING2 OVERVIEW  Determine whether a network communications problem is related to TCP/IP.  Understand.
1 © Fluke networks 2004 Everett WAMonday, May 18, 2015 Application Performance & Network Analysis Improving the end user experience.
QoS Solutions Confidential 2010 NetQuality Analyzer and QPerf.
Cold Fusion High Availability “Taking It To The Next Level” Presenter: Jason Baker, Digital North Date:
Reliability Week 11 - Lecture 2. What do we mean by reliability? Correctness – system/application does what it has to do correctly. Availability – Be.
Chapter Physical Database Design Methodology Software & Hardware Mapping Logical Design to DBMS Physical Implementation Security Implementation Monitoring.
Lesson 11-Virtual Private Networks. Overview Define Virtual Private Networks (VPNs). Deploy User VPNs. Deploy Site VPNs. Understand standard VPN techniques.
Hands-On Microsoft Windows Server 2003 Networking Chapter 6 Domain Name System.
Date: 03/05/2007 Vendor Management and Metrics. 2 A.T. Kearney X/mm.yyyy/00000 AT Kearney’s IT/Telecom Vendor Facts IT/Telecom service, software and equipment.
Hands-On Microsoft Windows Server 2003 Networking Chapter 7 Windows Internet Naming Service.
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network, Enhanced Chapter 7: Planning a DNS Strategy.
Information Technology Report Trey Felton Manager, IT Service Delivery January 2012 ERCOT Public.
25.1 Chapter 25 Domain Name System Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
Domain Name Services Oakton Community College CIS 238.
Implementing High Availability
IT Job Roles Task 20. Software Engineer Job Description Software engineers are responsible for creating and maintaining software of various different.
11 SYSTEMS ADMINISTRATION AND TERMINAL SERVICES Chapter 12.
11.1 © 2004 Pearson Education, Inc. Exam Managing and Maintaining a Microsoft® Windows® Server 2003 Environment Lesson 11: Introducing WINS, DNS,
Domain Name System | DNSSEC. 2  Internet Protocol address uniquely identifies laptops or phones or other devices  The Domain Name System matches IP.
1 Content Distribution Networks. 2 Replication Issues Request distribution: how to transparently distribute requests for content among replication servers.
Module 1: Reviewing the Suite of TCP/IP Protocols.
Solution Overview for NIPDEC- CDAP July 15, 2005.
Name Resolution Domain Name System.
Chapter 16 – DNS. DNS Domain Name Service This service allows client machines to resolve computer names (domain names) to IP addresses DNS works at the.
1. 1.Charting the CDNs(locating all their content and DNS servers). 2.Assessing their server availability. 3.Quantifying their world-wide delay performance.
1 Reading Report 7 Yin Chen 22 Mar 2004 Reference: Customer View of Internet Service Performance: Measurement Methodology and Metrics, Cross-Industry Working.
The role of ERE in Costumer Protection Eduard Elezi Albanian Regulatory Authority ERE Conference “Albanian Energy Sector, Challenges and Regulation” Tirana,
CcTLD Best Practices Michuki Mwangi AfriNIC5 - INET/AfTLD Meeting, Balaclava, Mauritius 30th Nov 2006.
Paul M Kane Director, Issues to think about! APTLD Members’ Meeting in Kuala Lumpur 1 – 2 March 2010 Contingency Planning.
Chapter 8 Implementing Disaster Recovery and High Availability Hands-On Virtual Computing.
AQS Development and Enhancement Plans AQS Development and Enhancement Plans AQS CONFERENCE Jake Summers June 9, 2010.
These materials are licensed under the Creative Commons Attribution-Noncommercial 3.0 Unported license (
POSTECH DP&NM Lab. Internet Traffic Monitoring and Analysis: Methods and Applications (1) 2. Network Monitoring Metrics.
70-291: MCSE Guide to Managing a Microsoft Windows Server 2003 Network, Enhanced Chapter 6: Name Resolution.
Domain Name System CH 25 Aseel Alturki
October 8, 2015 University of Tulsa - Center for Information Security Microsoft Windows 2000 DNS October 8, 2015.
POSTECH DP&NM Lab. Internet Traffic Monitoring and Analysis: Methods and Applications (1) 4. Active Monitoring Techniques.
W2K Server Installation It is very important that before you begin to install Windows 2000 Server, you must prepare for the installation by gathering specific.
DNS Security Pacific IT Pros Nov. 5, Topics DoS Attacks on DNS Servers DoS Attacks by DNS Servers Poisoning DNS Records Monitoring DNS Traffic Leakage.
Guide to Linux Installation and Administration, 2e1 Chapter 2 Planning Your System.
Performance Guard 4.1 Presentation Toll Free Dial In Number:(877) Int'l Access/Caller Dial In Number:(601) PARTICIPANT CODE: Doug.
242/102/49 0/51/59 181/172/166 Primary colors 248/152/29 PMS 172 PMS 137 PMS 546 PMS /206/ /227/ /129/123 Secondary colors 114/181/204.
1 Kyung Hee University Chapter 18 Domain Name System.
Is your Service Available? or Common Network Metrics Nevil Brownlee, CAIDA NANOG 19, Albuquerque, June 2000.
2.1 © 2004 Pearson Education, Inc. Exam Designing a Microsoft ® Windows ® Server 2003 Active Directory and Network Infrastructure Lesson 2: Examining.
* Agenda  What is the DNS ?  Poisoning the cache  Short term solution  Long term solution.
1 DNSMON DNS Server Monitoring RIPE NCC 3 December 2015.
Network design Topic 6 Testing and documentation.
PRACTICAL INTRODUCTION TO INTERNET TECHNOLOGY. Practical one PACKET DELAY AND LOSS IN INTERNET In this experiment, you will observe real delays and loss.
Performance Performance is about time and the software system’s ability to meet timing requirements.
11.1 © 2004 Pearson Education, Inc. Exam Managing and Maintaining a Microsoft® Windows® Server 2003 Environment Lesson 11: Introducing WINS, DNS,
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network, Enhanced Chapter 6: Planning, Configuring, And Troubleshooting WINS.
&. & DNS and IPv6 IPv6 Summit, Canberra 31st October & 1 st November 2005 Chris Wright, Chief Technology Officer &
1 Chapter Overview Monitoring Access to Shared Folders Creating and Sharing Local and Remote Folders Monitoring Network Users Using Offline Folders and.
Internet Naming Service: DNS* Chapter 5. The Name Space The name space is the structure of the DNS database –An inverted tree with the root node at the.
HighImpactSoft 2010 Organizing a Better Future. Agenda Specify Goals ScopeDefinitions Process Model Preliminary Requirements Issues and solutions TraceabilityPrototype.
Basics of the Domain Name System (DNS) By : AMMY- DRISS Mohamed Amine KADDARI Zakaria MAHMOUDI Soufiane Oujda Med I University National College of Applied.
Log Shipping, Mirroring, Replication and Clustering Which should I use? That depends on a few questions we must ask the user. We will go over these questions.
Homework 5 DNS 、 HTTPD 、 SNMP. Requirements One dedicated domain name for yourself Setup DNS server with following records  SOA, NS, MX  Make them reasonable.
DNS Domain Name System. Lots of people use the internet for different reasons. DNS Plays a big role in the internet. The DNS translates domain names into.
Internet Service Providers and types of internet connections
Understanding The Cloud
PROTEAN: A Scalable Architecture for Active Networks
Distributed Databases
VoIP & Hosted PBX
Chapter 25 Domain Name System
Chapter 25 Domain Name System
Presentation transcript:

Information Session DNS Service level recommendations and experiences

What is a DNS Service Level (or SLA)? SLAs are a measure of: The ability to resolve names in the name space The ability to obtain authoritative answers for domain delegations The time taken for changes in registry data to be reflected in the name servers

How to measure DNS Service Levels? These service levels are measured in a number of ways. Each has its own metric and recommended level and each deals with vastly different areas that effect DNS availability.

Service Level Measures: Overall Availability Per Name Server Availability Round Trip Time - RTT Packet Loss Average Resolution Time Scheduled Down Time DNS updates

Service Level Measures - Overall Availability This refers to the ability of an authoritative answer for DNS requests. Recommended SLA: 100%

Service Level Measures – Per Name Server Availability This refers to the availability of an authoritative answer for a DNS request from each name server individually. Recommended SLA: 99.99%

Service Level Measures – Round Trip Time & Packet Loss This refers to the ‘ ping ’ time and number of packets that ‘ go missing ’ in the network that the name server is connected to. Recommended SLA: 300ms/10%

Service Level Measures – Average Resolution Times This refers to the average response time for DNS queries from the time the query is received to the time the response is sent. Recommended SLA: 250ms

Service Level Measures – Scheduled downtime This refers to the amount of scheduled controlled total DNS downtime allowed. Recommended SLA: No downtime

Service Level Measures – DNS updates This refers to the addition, removal and modification of records in the name space, 5- 10min updates are not uncommon, but now days they are average, with providers able to offer instant DNS updates, and propagation using IXFR. Our Recommended SLA: 20mins Max

Recommended Service Levels Summary: 100% Overall DNS Availability 99.99% Per Name Server 300ms RTT (round trip time) 10% Packet Loss maximum 250ms average resolution time No down time 20 mins Max updates

How to confirm Service Levels are being met? Normally the registry operator will perform there own SLA monitoring and report back any variations to the governing body. However you may like to measure these things yourself.

Service levels such as: Overall Availability Per Name Server Availability Round Trip Time - RTT Packet Loss Average Resolution Time DNS updates Can be measured through ‘ sampling ’

Taking samples of each measurement over time periods is the easiest and most effective way to ensure service levels are being met. The frequency of these samples is flexible and can be decided between you and your registry operator.

Recommended sampling Frequency: Overall Availability ( 1 min ) Per Name Server Availability ( 1 min ) Round Trip Time – RTT ( 1 min ) Packet Loss ( 1 min) Average Resolution Time ( 1 min) DNS updates ( 10 min )

`Daily' Graph (5 Minute Average) Max Response Time: ms (0.4%) Average Response Time: 20.0 ms (0.1%) Current Response Time: 12.0 ms (0.0%) Example: Using mrtg to ‘ sample ’ Average Response Time

How to maintain good Service Levels? Choose excellent carry class data centres with redundant network connections, power etc Run multiple secondaries in diverse locations and networks Maintain a strong and up to date understanding of DNS Use clustering at each location Use quality hardware with different OS Maintain industry best practices, such as those stated in RFC2182, 2870 etc

How to co-operate with users to maintain service levels? Target larger commercial ISPs for secondary services Making use of the existing experienced DNS companies Keep up to date, and provide discussion lists so that you can hear your communities needs. Regularly participate in discussions and show you are taking responsibility for the Name space

In summary - key factors to maintaining SLAs are: Multiple secondaries Network carrier diversity Provider diversity Monitoring Accountability Maintain industry best practice and leverage existing industry experience

+ = Thanks for listening Any Questions?