Private Nameservers/Webhost's default Nameservers or Third Party DNS?

2 replies
Hi, I will be using HG's reseller hosting plan and set up my primary domain inside the account. I'm a bit confused when it comes to the best choice of setting up nameservers. I am given the options to either use HG's default nameservers, or set up my own private nameservers (i.e. ns1.myprimarydomain.com; ns2.myprimarydomain.com).
For both scenarios, they provided me with the same set of (two) IP addresses.

From a procedure point of view (for setting up private nameservers), I know that I would have to register the domain inside of Namecheap as private nameservers and make some DNS setting inside my HG account......but what confuses me is that a HG dude in a ticket made these comments:

"...setting up private name servers for your domains basically means that you would be administering your own DNS services. It would mean that you would need to verify that the service is up at all times."(*1)

"I can safely say that using our name servers(*2) will add another level of redundancy to your hosting."

"...it is best to have at least 2 name servers. It is actually best to have more than that if you would want to have a more fully redundant DNS service.
If you would like, you can even use google name servers, since they offer a dns service for users and since many users use google to search only it is usually a bit faster/more redundant since google has servers all over the world.
Our name servers are also load balanced in a similar fashion."


(*2) So what does he refer to exactly, by saying "using our name servers" (would add another level of redundancy to my hosting) -> THEIR name servers in terms of EITHER their default ones or private nameservers since both would be using the same IP addresses? OR...would he mean this in comparison to using THIRD PARTY DNS Services?

(*1) Also, what exactly would he mean by "you would need to verify that the service is up at all times" ?
Isn't it still their DNS Serviced I'd be using by setting up private nameservers (it's their IP's given to me for that!) ??
Or does he simply mean the details I will have to register with Namecheap (here: registering the domain as private nameservers)? But that's not a "service" that would need to be "verified to be up at all times"??

Also confused, as to when or why (and how) someone would be using a third party DNS service, i.e. Namecheap offers Nameserver set ups...

:confused: Any advice appreciated
#dns #private nameservers #registrar or hosting #webhost nameservers
  • Profile picture of the author wmguild
    It sounds like the HG tech is actually he one who is confused here. Virtual nameservers are just that - virtual - not real. They are simply masking the fact that your site is using the hostgator nameservers.
    {{ DiscussionBoard.errors[6216690].message }}
  • Profile picture of the author Rolliesworld
    Thanks, Larry & Bob. Glad to hear that you interpret it in the same way as I did.
    Just sad to realize that this was my first point of contact with HG and both tickets took hours to get a simple, straightforward reply to (first one took 6 hours, and I had even initiated a chat after the first 3, asking when to expect a reply...even that chat was ridiculously lame and unhelpful).
    The good thing that comes out of this is that by working through these things the hard way, makes you learn faster and build up a more comprehensive knowledge - lol.

    I now set up my primary domain as private nameservers, which means any subsequent cPanel accounts will be using them, too. Makes moving in the future easier, too.
    I only wonder if it was possible in the future to use different nameservers for just one particular domain (where all domains are under my reseller hosting account with HG) in this set up, or whether this is an "all or nothing" approach (i.e. all cPanel accounts under this reseller hosting will be using the private nameservers, or none)
    {{ DiscussionBoard.errors[6218172].message }}

Trending Topics