I will transfer my site to my new Interworx/Sago server, but want test the new box before transfer the domain name.
So I need to create a Siteworx account to start the tests. And as the site have a lot of databases and 1.200+ pages, I need do everything right now so I will have no need to delete this account and create a new one later.
As I?m new to Interworx, I have some questions.
This is what I think I should do. Is it right?
1 ? When I create the new Siteworx account need I to use the future domain name (for instance. mysite.com).
2 ? I will use the IP address (it will have a dedicated one) to access the test site. http://x.x.x.31/somepage.htm .
3 ? I will use the IP address to access the FTP.
4 ? After all is tested and ok I need only to change the DSN records at Network Solutions, wait propagation time and people accessing http://www.mysite.com will be seeing my Sago/Interworx server.
2 ? I will use the IP address (it will have a dedicated one) to access the test site. http://x.x.x.31/somepage.htm .
This will only work if you put the site on a dedicated IP (Sago gives ten so that’s fine, just make sure you set up the IP in NodeWorx as dedicated instead of shared).
3 ? I will use the IP address to access the FTP.
This is one way to do it but if you don’t want to put it on a dedicated IP, you can edit your computers DNS to use the DNS server on your server instead of your ISP’s. That is of course assuming your are using your own ns1 and ns2.myserver.com name server.
It’s probably easier to usee the dedicated IP.
4 ? After all is tested and ok I need only to change the DSN records at Network Solutions, wait propagation time and people accessing http://www.mysite.com will be seeing my Sago/Interworx server.
This is one way to do it but if you don’t want to put it on a dedicated IP, you can edit your computers DNS to use the DNS server on your server instead of your ISP’s. That is of course assuming your are using your own ns1 and ns2.myserver.com name server.
There is an other solution much better (at least for me) because you may navigate on the web without to have change again your DNS and you may have your website on a shared IP. This solution allow you to visite your website on the net and to access to your ftp account without have to wait for the World DNS update :
That’s just what I said (only you explained exactly how to do it). You are telling your computer to use your server’s DNS server instead of your ISP’s.
You are telling your computer to use your server’s DNS server instead of your ISP’s.
Not exactly tim…
Your method change the ISP dns. It causes that the user can’t go on the net anymore (normally)
My method doen’t change the DNS and doesn’t give my DNS but directly the IP of the hosted site. In fact, it’s like an add to the DNS from the ISP as all IP in the host file exceed these in the DNS. Also With this you may be on a shared or dedicated IP.
Thank you Guys, great answers and support. Fell much more comfortable now about the migration.
Also the Trick to acess the new host by the URL is very interesting. But I think that would be a problem. Would I lost access to the actual site, no? :rolleyes:
Anyway, no problem, as I have more IPs than I need and will give to the site a dedicated one.
Also the Trick to acess the new host by the URL is very interesting. But I think that would be a problem. Would I lost access to the actual site, no? :rolleyes:
No, you change it back when you are done.
Anyway, no problem, as I have more IPs than I need and will give to the site a dedicated one.
