What are the Benifits of Running Your Own DNS?

baileyjs asks: "I help run a small web development firm, and we are always trying to save money, but not at the cost of service to our customers. We currently purchase DNS services from our ISP, but are looking at getting our own rack. I was going to put some DNS servers there when I saw that Network Solutions offers free DNS. All our of domains (about 150) are currently on Network Solutions, so transfer is not an issue. Why shouldn't I use Network Solutions? Why should I build my own? What reasons, besides 'Network Solutions is Evil', can I give my boss?"

Comments

Re:Netsol costs more.

[metalmaniac1759]

I agree with you. I am adminstering a DNS server for my univ and it so happened that even before I could get my hands on BIND I was introduced to TinyDNS by some holy soul. Installing and configuring it is a cakewalk.

Then someday I had to configure BIND. I went crazy. It's got so many unnecessary things that you need to look into....

TinyDNS rocks.

Nandz.

Re:We used to host our own...

[RedHat Rocky]

Thanks to BINDisms, the question has to be asked: what component of DNS are you talking about?

Authoratative server: ie, answering queries for domains you control. The arguments for keeping this in-house are the same as any other mission critical service, not worth restating. If your company outsources critical functions, might as well outsource auth DNS as well.

Caching server: ie, collecting answers to queries for clients. This is an overlooked critical piece, IMO. Cache poisoning is a real security risk, better you rely on your own cache than your ISPs. And better if that cache is dnscache of the djbdns tools rather than BIND.