Moving from another server

[jennym]

Hi

I have two domains sitting on whb server, now I am in the process of bringing another two domains from another host to whb.

At the moment I am transfering the website files to my pc, and uploading them onto whb server.

I have clicked on the 'addon domains' link, and added the name of one domain but was told

Sorry, the domain is already pointed to an IP address that does not appear to use DNS servers associated with this server. Please transfer the domain to this servers nameservers or have your administrator add one of its nameservers to /etc/ips.remotedns and make the proper A entries on that remote nameserver.

Okay, so how do I get 'all my ducks lined up' before I point the domains to whb? I am trying not to have a gap. As soon as the dns gets pointed to whb I'd like the domains to be 'go'.

Would appreciate any advice - thanks

[Taras O.]

Hello,

As far as I understand you have a shared package with us, and if I'm correct and you are hosted on US based server, you can simply point the domain name to ns100.whbdns.com and ns101.whbdns.com.

Otherwise, we'll need to have your main domain name to advise you about this.

In case you want to use the name servers the domains are currently pointed to, we can add those name servers to remove DNS list and you'll be able to add the domains as addons. In order to request for this, please submit a ticket to our technical department at http://www.whbsupport.com and provide our engineers with the IP addresses of the name servers.

[jennym]

Thank you Taras for you quick reply. Yes you found me.

I think I understand, but to clarify, I can provide your engineers with the IP address of the two domains so they can make them as an addons - then when I am ready I point the domains to ns100.whbdns.com and ns101.whbdns.com?

This way, the switch is gapless.

I want to see the back of the servers that I am moving from having only been with them for just 2 months - one of the domains was moved to them from another hosting company which I had been with for about 8 years (problem was that they were not keeping up and were not listening). The average monthly visit stats for this domain have been consistant over the last year at about 800 to just over 1000 visits a day. Since moving the month of May was bad with about 600, but June looks like it is abysmal, Sunday being the pits, there were only 170 visitors. Looking at the server stats, the load was 279 (8 ucups) and even I couldn't get on the site all day.

They have one other domain name registered with them and I am hoping they are not going to be awkward when I ask for it.

Thanks for you help Taras. If I am wrong with my clarification, please let me know.

Regards, Jennifer

[Taras O.]

Yes, you are correct, but I'd give a more precise information. We'll need IP addresses of the name servers the domains are pointed to.

As for server load, the figures are nearly mind-blowing. Normal load for 8-core CPU is 9. 15 is something when server works more or less quickly. That's why we monitor servers 24x7 and don't allow the load to grow that high.

However, when you say about visits it makes me think a bit different way. The matter is that large number of visits can be something that server can easily go through if the website is lightweight, and in case of huge website this could be a nightmare. If your website is of the second type, I'd suggest you to take a look at our VPS plans. I can't say that it is something a shared server cannot bare, but taking into consideration aforesaid, we have to keep servers in high performance state and allowing all users to load the server heavily could cause the issue you've faced with on your old host. That's why having a dedicated environment would be a good idea. But again, if the website is quite heavy. I don't mention dedicated servers (which are the best solution in any case), as it is always worth saving a couple of bucks. But still a line of inexpensive dedicated server though (the most exensive box of the line is for $200/month).

Well, it is a parenthetic remark, now back to business.

Here is the way I'd suggest you to handle the transfer:

1. Submit the ticket to our technical department and provide them with name servers' IP addresses you are using at the moment.
2. Create addon domains and upload necessary files.
3. Change A and MX records on old name servers (this may bring some downtime depending on DNS zone TTL (time-to-live) set on old host).
4. Point domain names to our name servers, which will already contain needed records, right after you create addon domain.
5. Wait for DNS propagation. Shut down account on old host.

If something goes wrong (which won't be the case I hope) you can contact our team using the helpdesk: http://www.whbsupport.com.

That seems to be it.

If you have any questions, feel free to ask, my colleagues will gladly answer them.
And my shift is over and I'm going home

[Alan B]

If you have access to edit the DNS Zone on your current hosting server, you could reduce the SOA values now. Then wait several days, or more, before doing the transfer. If you allow sufficient days for the new SOA values to propagate, then that will reduce downtime once you do switch to the WHB server.