Analyst & Research Reports

If External DNS Fails, So Does Your Business

Issue link:

Contents of this Issue


Page 1 of 2

to get there. With naming and identity of people and machines so important to our Internet economy, DNS is the perfect connectivity and security glue. Part of the reason we changed our tagline was that uptime is no longer a factor—it's an expectation—for companies weighing DNS providers, but more so for their entire application. Key differentiators now focus more on availability, speed, security, and cost of the whole online infrastructure experience. How will my site perform? Will my users see latency delay? How consistent is their experience, and later, what's the reputation of my brand? These are the key questions customers are asking when they come to Dyn, across both our Internet Intelligence and Traffic Management families of products. Help with business continuity? Cloud vendor diversity? Threat prevention against DDoS attacks? We've got you Mr. Enterprise. Then Bob gets to the key question: "Should you do external DNS yourself?" [Note: we like this part because, for the most part, he answers with an emphatic NO]. He goes on to cite key reasons to source DNS externally from a managed DNS provider: ● Reliability/resiliency — design of platform and features ● Scale and scope/breadth of platform — number of POPs; it's a numbers game, and tough(er) to overload ● Performance ● Expertise, technical depth and constant evolution ● Responsiveness/continuous management ● Advanced features I don't think we really need to dive much deeper into this if you want our take on any one of these things, just check out some of those posts on our blog over the last eight years. We've been saying it since day one.

Articles in this issue

Links on this page

view archives of Analyst & Research Reports - If External DNS Fails, So Does Your Business