- 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
To Outsource or Not to Outsource
With all of the buzz and hype about the latest trend to outsource DNS service, there is much confusion on the topic. Is outsourcing really worth it? How expensive is it for an enterprise to run its own DNS server? Does a DNS Server create a lot of traffic? How intensive is DNS administration for the IT guys?Unsure about if outsourcing your DNS is worth it? Our latest tutorial on WebServer Compare defines some of the pros and cons of buying vs. building by using three examples of organizations with very different IT needs.
All of these questions raise pretty critical points, but they are also very difficult to answer without knowing the specifics about an enterprise.
In this tutorial, we will try to explain the pros and cons of outsourcing DNS management functions using three (general) examples of organizations with very different IT needs.
- Example No. 1 is a small office, home office (SOHO) or small business that has one server doing everything -- hosting its Web site, e-mail, files, and print capabilities. Its Windows 2000 server is running with 10 client access licenses. There is one IT professional on staff and one public IP address for the server.
- Example No. 2 is a midsize organization that has more than one server but not quite a server farm. It is running Unix and Windows NT/2000 on its servers and has claimed one or two public IP address for a few of its servers. The organization most likely has several full-time IT professionals on staff who look after the many workstations.
- Example No. 3 is a large enterprise with a dedicated staff of IT professionals running all different type of servers. It has a public IP address for every workstation and server as well as a large Server Farm occupying an entire area of building space.
The bottom line for any enterprise deciding whether to implement its own DNS service is that DNS itself doesn't create a lot of network or server load. DNS uses a simple database lookup and UDP packet system, some of the most basic things in the IT world.