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. Best, -ML
On Mon, Oct 5, 2009 at 12:17 PM, ML <mailinglists at mailnewsrss.com> 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. > > Best, > -MLIf you want to do more complex things, like subdomain delegation, split views, etc... Most ISP providers do not allow that sort of functionality, and the ones that do usually require that you submit requests through them (no web control panel) and it gets updated on their timeline. If you just need basic stuff with A, MX, CNAME, and other basic records, ISP DNS is just fine.
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. > > Best, > -ML > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >It depends upon how many PCs / servers you have and what functions these perform. If you only have one or two computers, do not run your own servers then you have no need for your own DNS. If on the other hand you have multiple servers and computer workstations and want to be able to connect to these by name then running DNS makes lots of sense. If you host your own web site and email etc then having your own DNS (or masquerade) saves bandwidth and more particularly time in DNS lookups. HTH -------------- next part -------------- A non-text attachment was scrubbed... Name: rkampen.vcf Type: text/x-vcard Size: 121 bytes Desc: not available URL: <http://lists.centos.org/pipermail/centos/attachments/20091005/16124e7a/attachment-0002.vcf>
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. >A) run a caching server to speed up lookups B) you want to have DNS for your private network behind a firewall. C) run your own authoritative DNS because you don't want to deal with funky outfits like godaddy. I belong to all three of these sets.
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 at gmail.com
> 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.Depends on the size of your organization. My at home setup has a few PCs & CentOS boxes so it's easy enough to manage host entries through the little gateway/router that I tweaked. The company I manage IT for OTOH, has close to 50 PCs & 6-7 servers (mixed Windows & CentOS) spread across three subnets and four offices. We use Active Directory so DNS resolution of our internal hosts is important. Two of the servers are also public facing (behind firewalls) so we have DNS setup to direct internal clients to the internal IP of the server & external clients access the public IP of the server. The internal DNS saves me and the staff from having to remember the mail server's IP and can just access it via the same name as the rest of the public. -- Drew "Nothing in life is to be feared. It is only to be understood." --Marie Curie
> 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 depends upon how many PCs / servers you have and what functions these > perform. > If you only have one or two computers, do not run your own servers then > you have no need for your own DNS.Yup. That's what /etc/hosts is for, and if I had under, say, a dozen or so systems, that's what I'd use. <snip> mark