- 1 Vapor IO Brings OpenDCRE to General Availability
- 2 VMware Takes the Wraps Off vRealize Automation and vRealize Business
- 3 Microsoft Previews Hyper-V Containers for Windows Server 2016
- 4 Mirantis Led FUEL Project Gets Installed Under OpenStack Big Tent
- 5 Red Hat Enterprise Linux 7.2 Adds Security, DR Features
Example 3: Large Enterprise Page 4
Example 3: Large Enterprise
Our third example is that of a large enterprise. It has back-up servers of every kind, or it is using clustering for its high-load systems, such as IMAP e-mail, file serving, and domain control. The enterprise already has a huge IT staff, and it's almost guaranteed that someone will be able to pick up DNS responsibilities with minimal training. More than likely, it will be the domain controller administrator who takes up this task, as the two services are very similar and can be intertwined in NT.
Outsourcing the DNS would be horribly inefficient in this case, as the enterprise has public IPs for each workstation and needs to dynamically update its DNS database as workstations go off and come online. Doing this with outsourced DNS services would be a waste of time and money. The only real way to have control over a large environment like this is for the enterprise to keep the DNS under its own control.