Crooked
02-05-2009, 08:12 AM
Hi all,
I/We signed up with a VPS host yesterday for a new website. The host has provided us with information for setting up a nameserver, but the problem is (other that I really have no experience with this) is that I'm not sure our (national) registrar allows private nameservers. I did speak to the registrar's tech support, but I'm not sure they understood me or if I explained it well. They said they did but it's really not working.
I'll talk to my host asap to see if I messed up somewhere with the nameserver setup on the server itself, but what I want to ask here is: I have a .com registered at GoDaddy - it's a small website on a shared host that I could move to the VPS, but don't have time right now - that's pointing to the shared host's ns; can I setup the private nameservers on the .com domain at GoDaddy, and still point that domain to the shared host?
In essence, the GoDaddy domain would also have a private nameserver, but I would use the shared host's ns for the actual website. I realize it may be a dumb idea, but if the new domain's registrar doesn't allow private ns, I'll have to think of something.
I/We signed up with a VPS host yesterday for a new website. The host has provided us with information for setting up a nameserver, but the problem is (other that I really have no experience with this) is that I'm not sure our (national) registrar allows private nameservers. I did speak to the registrar's tech support, but I'm not sure they understood me or if I explained it well. They said they did but it's really not working.
I'll talk to my host asap to see if I messed up somewhere with the nameserver setup on the server itself, but what I want to ask here is: I have a .com registered at GoDaddy - it's a small website on a shared host that I could move to the VPS, but don't have time right now - that's pointing to the shared host's ns; can I setup the private nameservers on the .com domain at GoDaddy, and still point that domain to the shared host?
In essence, the GoDaddy domain would also have a private nameserver, but I would use the shared host's ns for the actual website. I realize it may be a dumb idea, but if the new domain's registrar doesn't allow private ns, I'll have to think of something.
