DNS Marketshare - Alexa 10,000 + Fortune 500 - April 2013

This is a followup from last month's DNS marketshare post. In this post we use the same top 10,000 Alexa websites from last month (based on a 10 Mar 2013 Alexa snapshot). We then mined the DNS servers for each of these websites again using the same technique. The tables below represent the changes in marketshare and DNS hosting occurring during this time period (about 30 days).

New to this post is marketshare analysis for 2012 US Fortune 500 companies. This is a list published annually by Fortune Magazine ranking public US companies by gross revenue. For this analysis, we used the corporate websites listed for these companies on the CNN.com website. This marketshare analysis shows a very different provider makeup relative to top Alexa websites.

Notable during the past 30 days was a large scale DNS DDoS attack against spam blacklist provider spamhaus. To avert this attack, spamhaus switched DNS hosting to CloudFlare who successfully worked internally and with upstream providers to defend spamhaus against the attack as documented on their blog. The resulting positive press, appears to have attracted many new customers with their marketshare increasing by nearly 9% (22 Alexa 10,000 websites).

Fortune 500 DNS Marketshare - Apr 8, 2013

The following table provides a comparison of DNS provider marketshare between Mar 5 and Apr 8 2013 for the 2012 US Fortune 500 Companies.

ProviderRankWebsites (out of 500)MarketshareMarketshare Change
UltraDNS1357%+1 / +2.941%
Verisign DNS2244.8%0
Akamai3132.6%0
DynECT481.6%0
DNS Made Easy561.2%0
Savvis640.8%0
GoDaddy DNS740.8%0
Internap840.8%0
Rackspace Cloud DNS920.4%0
AWS Route 531020.4%+1 / +100%

Alexa Top 1,000 DNS Marketshare - Apr 8, 2013

The following table provides a comparison of DNS provider marketshare between Mar 5 and Apr 8 2013 for the top 1,000 Alexa websites.

ProviderRankWebsites (out of 1,000)MarketshareMarketshare Change
DynECT1787.8%+5 / +6.849%
UltraDNS2626.2%0
Akamai3494.9%+3 / +6.522%
AWS Route 534363.6%-1 / -2.703%
DNSPod5282.8%0
DNS Made Easy6212.1%0
GoDaddy DNS7131.3%0
Cotendo Advanced DNS8111.1%-1 / -8.333%
Verisign DNS9111.1%+1 / +10%
easyDNS10101%0
Rackspace Cloud DNS1180.8%0
CloudFlare1280.8%+2 / +33.333%
Enom DNS1370.7%0
Namecheap1460.6%0
Softlayer DNS1550.5%0
Internap1640.4%0
Savvis1730.3%0
Nettica1820.2%0
ClouDNS1920.2%0
ZoneEdit2020.2%0
DTDNS2110.1%0
EuroDNS2210.1%0
Worldwide DNS2310.1%0
No-IP2410.1%0
TAGS:
DNS Marketshare;
Alexa 10,000;
Alexa 1,000;
Fortune 500;
Dyn;
AWS Route 53;
UltraDNS;
DNSPod
Read More

DNS Provider Marketshare Summary - March 2013

Every few months we mine the DNS servers used by the top 10,000 Alexa sites. We then use various techniques including hostname and IP class C matching, and DNS lookup validations to correlate the DNS servers with specific DNS services like UltraDNS, Dyn and AWS Route 53. We call this point-in-time analysis a DNS marketshare snapshot. Finally we compare current and prior DNS marketshare snapshots to identify market trends and changes.

Steady DNS Outsourcing Trend

Outsourcing of DNS hosting to managed providers has grown consistently for Alexa 10,000 sites since we began capturing marketshare snapshots last year. Our analysis shows an increase of 6% in the past 4 months, and 15% in the past 11 months. Such growth appears to be favoring some services over others, with many even loosing marketshare. The following table provides a summary of managed DNS marketshare changes for the past 11 months. Only services with greater than 1% marketshare are displayed. The table is sorted by current Alexa 10,000 marketshare.

DNS Service Marketshare Change: Apr 2012 - Mar 2013
DNS ServiceService TypeAlexa 1,000 Marketshare ChangeAlexa 10,000 Marketshare Change
DynEnterprise5.1% to 7.1%+39%2.72% to 3.91%+44%
UltraDNSEnterprise5.7% to 6.2%+9%3.73% to 3.7%-1%
AWS Route 53Self Serve1.8% to 3.8%+111%1.68% to 3.56%+112%
DNSPodSelf Serve2.6% to 2.2%-15%3.4% to 3.1%+9%
GoDaddySelf Serve1.5% to 1.3%-15%2.89% to 2.89%+0%
CloudFlareSelf Serve0.3% to 0.6%+100%0.92% to 2.56%+178%
DNS Made EasySelf Serve2% to 2.1%+5%2.47% to 2.43%-2%
AkamaiEnterprise4.2% to 4.7%+12%1.84% to 2.06%+12%
Rackspace Cloud DNSSelf Serve1.3% to 0.7%-86%1.48% to 1.61%+9%
VerisignEnterprise0.7% to 1%+43%0.7% to 0.97%+39%
easyDNSSelf Serve0.6% to 1%+67%0.82% to 0.79%-4%
Cotendo (acquired by Akamai)Enterprise2.1% to 1.2%-75%0.76% to 0.6%-27%

Alexa Top 1,000 DNS Marketshare - Mar 5, 2013

The following table provides current marketshare analysis for the top 1,000 Alexa website based on a snapshot taken on March 5, 2013.

ProviderRankNumber of SitesMarketshare Change
Nov 2012 to Mar 2013
Market Share %
Dyn Enterprise171+107.1%
UltraDNS262+36.2%
Akamai347+64.7%
AWS Route 53438+133.8%
DNSPod52202.2%
DNS Made Easy621-42.1%
GoDaddy713-11.3%
Cotendo812-61.2%
EasyDNS910+21%
Versign1010+21%
Rackspace Cloud117-20.7%
CloudFlare126+10.6%
eNom136-30.6%
Namecheap145+10.5%
SoftLayer15500.5%
Internap164+10.4%
Savvis173-10.3%
Nettica182-20.2%
ClouDNS19200.2%
ZoneEdit202-30.2%
EuroDNS22100.1%

Alexa Top 10,000 DNS Marketshare - Mar 5, 2013

The following table provides current marketshare analysis for the top 10,000 Alexa website based on a snapshot taken on March 5, 2013.

ProviderRankNumber of SitesMarketshare Change
Nov 2012 to Mar 2013
Market Share %
Dyn Enterprise1391+523.91%
UltraDNS2370-173.7%
AWS Route 533356+573.56%
DNSPod4310-23.1%
GoDaddy5289+112.89%
CloudFlare6256+772.56%
DNS Made Easy7243-42.43%
Akamai8206+252.06%
Rackspace Cloud9161+31.61%
Versign1097+190.97%
SoftLayer1182+30.82%
Easy1279-10.79%
Namecheap1373+140.73%
eNom1470-100.7%
Cotendo1560-70.6%
Savvis164300.43%
ZoneEdit1734-60.34%
DynDNS1830-20.3%
Internap1929-10.29%
Nettica2028-30.28%
ClouDNS2119+30.19%
Zerigo DNS231200.12%
No-IP249-60.09%
EuroDNS258+10.08%
TAGS:
DNS Marketshare;
Alexa 10,000;
Alexa 1,000;
Fortune 500;
Dyn;
AWS Route 53;
UltraDNS;
DNSPod
Read More

Comparison and Analysis of Managed DNS Providers

Introduction

This blog post is the culmination of year's effort researching and developing methods for analyzing and comparing managed DNS services. During this time, we provided access to our analysis and solicited feedback from any DNS provider that would listen. We would like to thank our contacts with UltraDNS, Cotendo, Amazon Web Services and NetDNA for the feedback they provided. As always, it is our intent to provide objective, fair and actionable analysis. We have not been paid by anyone to conduct this testing or write this post. If you have feedback, we'd like to hear it.

This blog post is also intended as an introduction to a new monthly report entitled State of the Cloud - DNS available for purchase on our website. The full version of the August 2012 edition of this report is available for free in pdf format (10MB). Future editions of this report will include both free and premium editions where the free version will include everything but some of the more advanced content such as marketshare analysis. This blog post provides an introduction to and summary of the August 2012 edition of this report.

View Full Report (PDF)

What is DNS?

Domain Name System or DNS for short, is the part of the Internet that lets users access websites (and other Internet services) using easy to remember words and phrases called hostnames like amazon.com or google.com. Without DNS, users would be required to use cryptic numeric-based identifiers called IP addresses (e.g. 72.21.194.1). When a user types a hostname into their browser address bar, one of the first steps undergone is to translate the hostname to an IP address. This translation process involves querying a DNS server that has been assigned responsibility for that hostname. These are called authoritative DNS servers. If the authoritative DNS server is not accessible, the browser will be unable to resolve the IP address and display the website.

DNS server software is freely available and is not overly complex to setup or run. The core functionality of a DNS server is simpleā€¦ the translation of hostnames to IP addresses. It requires only minimal bandwidth and CPU resources to maintain a DNS server. Many organizations host their own DNS servers without much effort.

Managed DNS

Managed DNS is a service that allows organizations to outsource DNS to a third party provider. There many reasons why an organization may elect to outsource DNS hosting... here are a few:

Whatever the reasons are, managed DNS is a fast growing sector in the cloud.

Enterprise versus Self Service

Managed DNS providers can be generally divided into two categories:

After speaking with multiple enterprise providers, it is our impression that they generally consider self service providers as non-competitors targeting a different customer demographic.

Comparing Managed DNS Services

Comparing DNS services is not as simple as running a few benchmarks and calling it good. There are multiple criteria where comparisons may be drawn. In this post, we'll present some criteria we believe to be relevant, the techniques we have used to implement them, and the resulting analysis. The following DNS providers are included:

TAGS:
DNS Performance;
DNS Availability;
DNS Marketshare;
Dyn;
AWS Route 53;
DNS Made Easy;
UltraDNS;
easyDNS
Read More

Is Joyent Really 14X Faster than EC2 and Azure the Fastest Cloud?

Many are skeptical of claims that involve benchmarks. Over the years benchmarks have been manipulated and misrepresented. Benchmarks aren't inherently bad or created in bad faith. To the contrary, when understood and applied correctly, benchmarks can often provide useful insight for performance analysis and capacity planning. The problem with benchmarks is they are often misunderstood or misrepresented, frequently resulting in bold assertions and questionable claims. Oftentimes there are also extraneous factors involved such as agenda-driven marketing organizations. In fact, the term "benchmarketing" was coined to describe questionable marketing-driven, benchmark-based claims.

This post will discuss a few questions one might consider when reading benchmark-based claims. We'll then apply these questions to 2 recent cloud related, benchmark-based studies.

Questions to consider

The following are 7 questions one might ask when considering benchmark-based claims. Answering these questions will help to provide a clearer understanding on the validity and applicability of the claims.

  1. What is the claim? Typically the bold-face, attention grabbing headline like Service Y is 10X faster than Service Z
  2. What is the claimed measurement? Usually implied by the headline. For example the claim Service Y is 10X faster than Service Z implies a measurement of system performance
  3. What is the actual measurement? To answer this question, look at the methodology and benchmark(s) used. This may require some digging, but can usually be found somewhere in the article body. Once found, do some research to determine what was actually measured. For example, if Geekbench was used, you would discover the actual measurement is processor and memory performance, but not disk or network IO
  4. Is it an apples-to-apples comparison? The validity of a benchmark-based claim ultimately depends on the fairness of the testing methodology. Claims involving comparisons should compare similar things. For example, Ford could compare a Mustang Shelby GT500 (top speed 190 MPH) to a Chevy Aveo (top speed 100 MPH) and claim their cars are nearly twice as fast, but the Aveo is not a comparable vehicle and therefore the claim would be invalid. A more fair, apples-to-apples comparison would be a Mustang GT500 and a Chevy Camaro ZL1 (top speed 186).
  5. Is the playing field level? Another important question to ask is whether or not there are any extraneous factors that provided an unfair advantage to one test subject over another. For example, using the top speed analogy, Ford could compare a Mustang with 92 octane fuel and a downhill course to a Camaro with 85 octane fuel and an uphill course. Because there are extraneous factors (fuel and angle of the course) which provided an unfair advantage to the Mustang, the claim would be invalid. To be fair, the top speeds of both vehicles should be measured on the same course, with the same fuel, fuel quantity, driver and weather conditions.
  6. Was the data reported accurately? Benchmarking often results in large datasets. Summarizing the data concisely and accurately can be challenging. Things to watch out for include lack of good statistical analysis (i.e. reporting average only), math errors, and sloppy calculations. For example, if large, highly variable data is collected, it is generally a best practice to report the median value in place of mean (average) to mitigate the effects of outliers. Standard deviation is also a useful metric to include to identify data consistency.
  7. Does it matter to you? The final question to ask is, assuming the results are valid, does it actually mean anything to you? For example, purchasing a vehicle based on a top speed comparison is not advisable if fuel economy is what really matters to you.