Welcome to the myhosting.com Forums.
Nameserver records for VPS
Hi everybody, I just bought a VPS and already migrated one of my hosted websites using the cpanel import feature and it went seamless.
The problem is that when I setup the nameservers at name.com they cannot resolve to a domain, I already checked wikis, blogs, etc about the proper NS for websites hosted in my VPS and no luck using ns1.myhosting.com, ns2.myhosting.com, ns11.myhosting.com, ns12.myhosting.com
The thing is that I read somewhere that I need to email them to add my domain name to above nameservers for it to work.
My question is: do I need to email them for each of my 90 domains currently hosted at the other server?? With my current hosting provider, I just add the domain name in cpanel and enter my custom ns records in name.com and voila, its done!!
Is it really a manual process each and every time? or is it a one time only process??
What is making me worry is the fact that my current VPS provider (Servint) replies to service tickets in a matter of minutes, and myhosting sometimes takes half a day or more!! Please advise, is this the way myhosting.com works? Should I stay with my current VPS provider even though is more expensive? Thanks!!
I`ll submit your problem to myhosting staff, i hope they can help you ASAP
To advise, our cpanel vps servers are standalone systems and DNS is not integrated. You can either use DNS setup on the VPS itself and point your nameservers to your VPS, or you can add your domains into our onCloud control panel which will provide DNS however you will need to modify the DNS manually there.
DNS on VPS pros:
-Simplified solution so management of DNS occurs only from within cPanel and propagates everywhere.
DNS on VPS cons:
-Running Bind or any other DNS solution will use resources, so it does place additional load on your VPS to do this.
-Some registrars require verified nameservers. In this scenario, this simplest workaround is to use a combination of both DNS on VPS and DNS in myhosting.com. What you would do is direct your nameservers to myhosting.com DNS, but in your DNS, specify a second set of NS records for all subdomains. This way changes you make in cpanel will reflect.
DNS on myhosting.com DNS pros:
-Registered nameservers, compatible with all registrars.
DNS on myhosting.com DNS cons:
-Requires DNS be modified in myhosting.com onCloud Control Panel to match what configuration in cPanel specifies.
This is where I am currently stuck, and rather than assume I've done a step correctly I'd rather someone with experience give a proper solution. Can a step by step walkthrough be posted here for DNS setup on VPS?
Originally Posted by jeremya
-steps in myhosting.com onCloud Panel
-steps in cPanel
Kinda sad that I'm having to read FAQ files on other company websites... But... is this correct?
The nameservers must always belong to a domain that is hosted on the VPS. Therefore if all my domains are currently at an external registrar then my only solution is to email support and have them add my primary domain to the MyHosting DNS manually, before I can even use my primary domain as a private DNS in cPanel?
So with the two options previously mentioned, I've created a wiki to assist you through either option.
Hope that helps clarify things! Keep in mind, the reason this particular item is a bit confusing perhaps is that a cPanel VPS is essentially a standalone service. There is no integration myhosting.com onCloud for cPanel/WHM. Integration is limited to VPS container modifications and cPanel/WHM is simply installed on top of that as if you did it yourself.
We do of course handle all of the licensing and the original install
Thank you Jeremya.
Originally Posted by jeremya
By WrigleyF in forum Off Topic
Last Post: 2011-03-31, 02:45 PM
By WrigleyF in forum Promotions, Sales, Billing
Last Post: 2011-01-18, 09:00 AM
By Rusher in forum Virtual Server
Last Post: 2010-07-27, 10:22 AM
By Tenk in forum Troubleshooting
Last Post: 2010-05-01, 03:22 PM
By teemo in forum Troubleshooting
Last Post: 2009-05-25, 04:13 PM