DNS - Hosting your own name server PROS & CONS
I have a recently set up a dedicated server and am hosting about 70 domain names on it. I am not offering shared hosting to the general public - so the domain name records are not going to change often - just if I need to actually move things around like split email serving off onto another server, etc.
Anyway, at the moment most of the domains have their DNS records hosted on register.com's name servers. I think that is working OK. The register.com site's user control panel is slow and clunky - it would certainly be easier to be editing the zone record files myself through webmin on my own server. But this is hardly a big worry for me - because, like I said, the domains DNS records are pretty much set and forget.
1) So my newbie question to you gurus is - should I even consider setting up bind9 and running named on my dedi server and hosting the dns records locally? What are the pros and cons I should consider?
2) Also - I don't really understand how name servers work - although I am quite comfortable with the idea of editing the zone record files. What I don't understand is how the secondary DNS hosting works. I have always just used my domain name registrar to handle DNS hosting. With the second, third, forth, etc nameserver - are the zone records sort of automatically mirrored and updated from the primary name server - or is it a matter of replicating things yourself?
3) How much will running a name server add to my bandwidth comsumption if I were to do so?
