Any good reason why you should run your own nameservers?

[ChrisGuthrie]

I have a dedicated server but have continued to just use the name server through my host and not my own name server.

Any particular reason why I should not be doing this and should instead use my own name server for DNS records?

 

[ChrisGuthrie]

no takers?

 

[andreyknure]

As far as I know the reason for which private nameservers may be required is that you don't wish to show other people the company, where your site is hosted. Private nameservers are usually ordered by hosting resellers who would like to represent their own solutions. That is the only reason that I know.

 

[Kate]

There are a few good reasons, one is that if you switch to another hosting company, you need to change the DNS for all the domains hosted there, and if you use a crappy registrar like 1&1 with no bulk management it would be more time-consuming...
Instead you can use your own DNS for your domains to point them to some host, then if you decide to switch to another webhost you just have to change the A records etc in your own name servers. You don't have to update the depending domains.

The other reason is when you need more flexibility than offered by your registrar. For instance certain features or types of records may not be available on all platforms.
Also you may want more redundant/robust DNS.

 

[abdussamad]

SDsinc basically covered most of the benefits. The ease of switching hosting providers is the best reason. I have one point to add though.

Basically if you keep your nameservers on a server separate from where your sites are hosted you increase the chances of downtime. The reason being that instead of requiring just your dedi to be up you now also need your nameserver's server to be up too.

In case your thinking that the likelihood of your hosting provider's nameservers being down is low think again. Every host suffers downtime. Just recently namecheap, a rather large and successful registrar, suffered downtime on its DNS servers. Also recently edit dns suffered a DDOS attack on its DNS servers. So its best to use your private nameservers hosted on your dedicated server along with your websites.

 

[FanCube]

Handling your own DNS server has pros and cons (surprising enough )

In general most people underestimate the skills needed to run a professional and efficient DNS service. Many users think DNS is something you click "Yes" to in control panels like cPanel, it's not! Even that cPanel alike solutions will work decent for most users.

Typically if you run your own DNS from your own box, you will have both NS1 and NS2 on the same machine which obviously is not the optimal solution as DNS servers should be located at different physical locations.

A reason why you would want to run your own DNS service is branding. When someone do a whois look up they will see ns1.YourCompany.com etc. This is important to some and not to others.

Today there are a bunch of DNS services with web interfaces etc. providing first class DNS service for free. Some are even good at handling domains in bulk as they offer the opportunity to setup templates etc.

Unless you have very specific needs, knows how to run a DNS service and does not need the branding you should probably look into third party DNS services.

 

[duodec]

...
Typically if you run your own DNS from your own box, you will have both NS1 and NS2 on the same machine which obviously is not the optimal solution as DNS servers should be located at different physical locations.
...

AND should be in different subnets and also connected via different internet service connections that are, if possible, from different providers; all these work together to minimize the chance of a single point of failure taking out all of your name servers.

 

[coltter]

There are a few good reasons, one is that if you switch to another hosting company, you need to change the DNS for all the domains hosted there, and if you use a crappy registrar like 1&1 with no bulk management it would be more time-consuming...
Instead you can use your own DNS for your domains to point them to some host, then if you decide to switch to another webhost you just have to change the A records etc in your own name servers. You don't have to update the depending domains.

The other reason is when you need more flexibility than offered by your registrar. For instance certain features or types of records may not be available on all platforms.
Also you may want more redundant/robust DNS.

Well said, if you dont want to let someone know where your site is hosted, then switch to your own domain nameserver.

 

[DomainMOD]

Well said, if you dont want to let someone know where your site is hosted, then switch to your own domain nameserver.

Using custom DNS servers doesn't really hide who you're hosted with. A quick lookup on arin for your domain's IP and they'll be able to see who owns that block of IPs.