Every IT organization on the planet wants to get by with the network infrastructure they have. Change is hard, and inherently risky. There has to be a pretty big reason to go in a different direction.
The Domain Name System (DNS) is no different. Most organizations start off with a simple, out of the box Microsoft DNS solution. For the number of DNS zones and DNS servers in most small networks, it probably works fine. It’s the default choice for Active Directory, so everything seems natural.
Yet there will inevitably come a time when the cost of free network infrastructure management is simply too high. As organizations scale, as strategic initiatives introduce more complexity, as workloads grow, all of the downsides of a Microsoft DNS infrastructure begin to show themselves.
Suddenly, the network seems fragile – errors and configuration issues in DNS entries often lead to downtime. Suddenly, the number of DNS queries grows dramatically and you have limited visibility into what’s happening on the network – either your external DNS or your internal DNS. Suddenly, even the “overlay” solutions you put in place start to fail. It’s at these times that all those Microsoft DNS issues start to cascade.
What are the symptoms of a system weighed down by Microsoft DNS? We put this handy chart together to demonstrate some of the operational challenges we see with customers of ours who are getting ready to migrate away from Microsoft DNS.