In the first white paper in this series, The DNS Appliance Imperative, I argued that the evolution of the Domain Name System demanded that it move to an appliance platform. DNS is now critical to the operation of nearly every non-trivial networked application. DNS has also become dauntingly complex, both in theory and in its implementations. And unfortunately, hackers increasingly target DNS infrastructure. This confluence of factors isn’t unprecedented—it’s the same combination that drove IP routing, network storage, and firewalls to appliance implementations, because only appliances could deliver the requisite simplicity of management, reliability, and security.But how are appliances deployed effectively in the real-world? In this case study, let’s take a look at a corporate DNS architecture based on industry best practices. The design will consider the company’s requirements for availability, security, and disaster recovery; network topology; administrative staff and structure; other protocols, including DHCP; and the need to support Active Directory.
Over the course of the paper, we’ll examine how the features of appliances enhance yet simplify this DNS infrastructure, making it more secure, more reliable, and less costly to manage and maintain.
While reading this paper, consider your own DNS infrastructure. Does it provide the same level of resiliency and security? Could the use of appliances enhance your infrastructure? Are there aspects of this design that you could adapt to your own use?
Privacy Statement: Information submitted through this form will only be used by Infoblox for the purpose of informing you about products and services.
