Un-disrupt the Cloud Disruption
Cloud initiatives are great for end-users, but a nightmare for network administrators who have to deal with the DNS consequences.
Key takeawaysThis key takeaway was generated through LLMs crawling the page and coming up with an overview of the content.The article reports on BlueCat's March 21 "Un-disrupt the Cloud Disruption" event in Toronto, where technology leaders discussed how cloud adoption is overwhelming traditional network teams and driving teams to build risky workarounds. It highlights that centralized DNS automation, using a single authoritative database and APIs or BlueCat’s Gateway platform, can restore control by enabling self-service and consistent workflows across AWS, Azure, and hybrid environments. The piece emphasizes that implementation effort is often less than organizational sign-off time—migrations can be implemented quickly once stakeholder approvals are secured—and points readers to BlueCat events for further discussion.
Why is cloud adoption creating problems for traditional network teams according to the article?
The article explains that cloud adoption accelerates the rate of change and dramatically increases inbound DNS service requests, overwhelming traditional network teams who previously managed such requests manually. When IT teams cannot keep pace, business units, developers, or project leads bypass central teams and create their own network workarounds, which leads to loss of control, governance and compliance issues, and system instability. The core problem is a mismatch between the speed of cloud-driven change and the capacity of manual, ticket-based network processes.
How does the article describe centralized DNS automation as a solution?
Centralized DNS automation is presented as the scalable solution that preserves control while enabling speed. The approach uses a single, authoritative DNS database and exposes consistent APIs or automation through platforms like BlueCat’s Gateway so stakeholders can perform standard tasks via self-service. This creates one standardized workflow for creating DNS records that abstracts differences between cloud providers—so the same process works whether workloads are on AWS, Azure, or span multiple systems—reducing errors, improving governance, and supporting rapid change.
What does the article say about the effort and timeline to implement centralized, automated DNS?
The article emphasizes that technical implementation of a centralized, automated DNS architecture is often faster than the organizational approvals required around cybersecurity, budget, and procurement. It cites a customer example where stakeholder sign-off took three months, but the actual migration implementation required only one week. Even with labs and sandboxes, external clearance and managing dependencies typically consume the most time, while the network-side deployment can be relatively quick once approvals are in place.
The cloud delivers amazing new capabilities for end-users and enterprises. It also exacts a cost on network teams managing the back-end. On March 21, BlueCat hosted Toronto technology leaders to talk through the implications of the cloud on network teams. This “Un-disrupt the Cloud Disruption” session featured a lively discussion between Jason Grant, founder of the Automated Method, and BlueCat CTO Andrew Wertkin. Here are some highlights from the discussion, which was also highlighted in IT World Canada.
“Innovate faster”
Everyone seems to agree that large organizations today have one business requirement: innovate faster.
In the recent past, that meant hiring more network administrators to manage inbound DNS service requests. With the advent of the cloud, the deluge of service requests became so overwhelming that the old model simply couldn’t catch up – there aren’t enough networking professionals in the world to handle all the DNS tickets.
Wertkin summed up the operational risk like this: “If traditional IT teams can’t match that rate of change, the business is just going to go around them. The people pushing out new virtual private clouds on AWS or networks on Azure aren’t going to wait around for a help desk ticket for somebody to assign the new network.”
This is when the network team loses control of the enterprise – when project leads and developers start to build their own workarounds. According to Wertkin, “that causes all sorts of issues – not just governance and compliance issues, either. Stuff breaks, because the system can’t cope with such rapid change.”
One DNS to rule them all
The better way – perhaps the only way – to keep up with this new pace is network automation through DNS. With a centralized core DNS architecture, BlueCat enables organizations to automate a range of standard tasks, pushing those out to stakeholders through a self-service portal.
Wertkin frames the new approach to DNS management with automation in place: “There’s one way to create a new DNS record here. I don’t care where that thing ends up. Here’s the API. Create some sort of abstraction to these different technologies because the one thing we know for sure is if a workflow is on AWS today, it might be on Azure sometime in the future. It might end up spanning two different systems. So, from an infrastructure standpoint we need something that’s common, and DNS is one of those common elements.”
Speakers and participants alike agreed that the key to DNS infrastructure in the age of cloud is flexibility. With a standardized system for DNS running through a single database of records, you can run just about any automation use case through an API or BlueCat’s Gateway automation platform.
Get started with network automation
Centralizing and automating DNS sounds like a big task. Everyone appreciates the potential benefits of DNS automation, but many question the level of effort to get there.
The response was telling: for most BlueCat customers, getting sign-off from outside stakeholders in cybersecurity, budget, and procurement often takes far longer than getting a centralized, automated DNS architecture up and running. Citing a recent customer example, it took three months for everyone outside of the network team to sign off on a migration strategy. It took one week to actually implement that strategy.
Even customers with labs, sandboxes, and pre-production environments struggle with outside clearance for network changes. Working through the dependencies, the project managers – this is what takes the most time.
Wish you were at our Un-disrupt the Cloud Disruption dinner? Check out our Events page for upcoming discussions about DNS in your area.
Published in:
BlueCat provides core services and solutions that help our customers and their teams deliver change-ready networks. With BlueCat, organizations can build reliable, secure, and agile mission-critical networks that can support transformation initiatives such as cloud adoption and automation. BlueCat’s growing portfolio includes services and solutions for automated and unified DDI management, network security, multicloud management, and network observability and health.
Related content
How to map your network with user-defined links in Integrity X
Map your network with user-defined links in Integrity X to define and manage custom relationships, such as dual-stack and NAT environments.
Automate your DDI modernization path by migrating with Micetro
Automate cross-platform DNS and DHCP migration with Micetro to reduce risk, eliminate manual effort, and modernize infrastructure faster.
Your journey to intelligent NetOps begins at Cisco Live
Visit BlueCat’s booth or book a meeting now to learn more about how our solutions can help you build a network that supports constant change.
Replace BIND and ISC with Micetro DNS/DHCP Server (MDDS)
Tired of patching and manually configuring BIND DNS and ISC DHCP? Discover how Micetro MDDS appliances can replace them for modern DDI.