All great responses.
Why would a small business want to run their own DNS? Independence and control.
If you want or require the ability to route people to internal (on your LAN/WAN) web-based applications to URL's like http://intranet or https://yourcompanyquickenbooks this is one way rather than having your employees try and remember things like https://10.1.1.1 or maintaining a bunch of lmosts (Win) and /etc/hosts (*nix) files on workstations and laptops. Or if you have trouble frequently with your ISP's DNS servers (Comcast or whoever) this is a simple way to go (caching). Make sure you secure it and have it nicely hidden in a DMZ or on your internal net through. One snag to keep in mind is that if you have your internal server acting authoritatively for yourcompany.com and externally it is a different SOA you could run into overlap issues. But in general the reason is that most companies have stuff in their internal DNS they certainly do not want known in the public and want to manipulate resolution internally for some things. But if your business can live without the be
nefits or protection that running your DNS server internally brings, then really no need to add another server to your admin duties unless you are really excited to manage a DNS server or tackle some complex and uber-secure Master/Slave architecture as a project. Hopes this helps.
Larry Kemp
Network Engineer
U.S. Metropolitan Telecom, LLC
Bonita Springs, FL USA
-----Original Message-----
From: centos-bounces@xxxxxxxxxx [mailto:centos-bounces@xxxxxxxxxx] On Behalf Of Les Mikesell
Sent: Monday, October 05, 2009 12:31 PM
To: CentOS mailing list
Subject: Re: DNS Serving - Why my own?
ML wrote:
> HI All,
>
> Can anyone explain why I might want to run my own DNS Server in-house?
> I have a comcast business circuit and use their DNS servers and when I
> need entries, I use GoDaddy where I buy my domains.
It's generally a good idea to have a caching server locally for speed
and if you use NAT and private addresses, the same server(s) can be
primary for the internal view of your domain.
If you aren't a large enterprise with multiple server sites, you might
be better off letting a service provider handle the public view.
--
Les Mikesell
lesmikesell@xxxxxxxxx
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
