suggestions | migration

Hello

If possible i want to know some feedback from you guys for a migration we want to do.

What is the recomended process for transfering a domain from one control panel to another. By this i mean, moving a domain between cp’s. We have a login that we use for clients who do not need to ue a control panel, we have several clients in there and we manage it for them.

I want to move this domain to a cp where the domain will be by it self.

How would you guys do it?

i was thinking.

1-Creating new cp login
2-Backing up site via ftp
3-Downloading emails pop3
3-deleting domain
4-creating domain
5-upload files
6-transfer emails back to each account by creating an imap on outlook express.

Questions for JODO:

Will dns propagation be an issue?
Can jodo help in the migration of email accounts with emails included, address books contacts, whitelists etc.. ?

Any feed back is welcome.

thanks!

erik

How many mailboxes to be moved here?

still making a list i will update you when we have it ready. should be around 50…

but let me find the exact figure..

ok i went through the list and it is 30 email accounts that should keep the same settings, of webmail, contcts etc..

thanks

If you can exclude horde prefs/contacts and antispam settings(not whitelist/blacklist), I can offer some help (this is normally a paid service).

their is only like 1 or 2 accounts that use squirel mail with those sort of settings.

I will maek a list of the emails and send them to you via pm.

thanks for the help.

Erik

I too need to move several domains from a shared account to individual accounts. In my case, websites and mailboxes are not a problem as each website consists of just a holding page, and all mail is forwarded to the client’s ISP hosted mailboxes.

However, the new accounts are on a different server than previously and so DNS propagation delays are causing a problem with email delivery. Most of my clients can not afford to have mail sent to them being bounced for up to 48 hours.

I’ve learnt my lesson, and will not be using a shared account for multiple clients again - no matter how small they might be at sign-up.

I contacted live chat and their best suggestion was to do the changes over a weekend. Unfortunately that is not a suitable work-around for some clients. Is there any other way to mitigate the propagation problem?

sadly no :frowning:

their is 1 thing I do not understand on the dns propagation on each domain.

For example I eliminate 1 domain ( no mail accounts ) with 10 subdomains and add the domain in another control panel. the DNS would have to propogate 24 - 48 hours ?

thanks!

most ISPs have DNS cache that is 24-72 hours.

but the dns of the domain will not change we are just switching from one control panel to anohter inside my own account.

how would the dns cache afect if nothing changes but the location of the control panel.

I’m beginning to think this is not a propgation issue. There has been no change in DNS servers. The only difference is that there is a change of which Jodohost server the domain is hosted on. The shared account was on web5, the new account is on web7.

When changing from one host provider to another, the new site becomes avaliable within 1 hour of updating the DNS server info. Why should it take so much longer when no DNS changes are involved?

[quote=“nzkiwi, post: 46084”]
I’m beginning to think this is not a propgation issue. There has been no change in DNS servers. The only difference is that there is a change of which Jodohost server the domain is hosted on. The shared account was on web5, the new account is on web7. QUOTE]

Very good point..

but the domain will still be pointing over to jodo, it would be jodo’s dns server who needs to update.

But, that does require a DNS change. The domain name pointed to one server at Jodo before, now it needs to point to a different server.

DNS is like a big library card catalog–a domain name is just a pointer/reference to an IP address (tied to a server). Changing servers means updating the “card catalog” in the same way that moving a book from one library shelf to another requires an update.

DNS propagation time is an “up to” amount…it can take up to ## hours, but it doesn’t have to. If no one on your ISP’s network has requested the URL within your ISP’s timeout interval, their server won’t know the target IP address. So, the DNS lookup will be passed up the chain to find an authoritative server (probably the top-level servers, which won’t actually know the server address so they will ask Jodo’s DNS server).

I’ve had changeovers happen instantly. I’ve had them take more than 72 hours. Sometimes your PC caches the DNS, too. If you’re on Windows, open a command prompt and type ipconfig /flushdns (I don’t know the Linux or Mac equivalents but they’re probably similar).

Tim

A peculiarity of the ISP I use is that their caching is updated approximately hourly. Having updated moved dozens of sites from one host to another, I am able to vouch for this fact.

In all the 25 or so domains I have moved to Jodohost over the past 6 months, the average delay was about 30 minutes. The one domain I have moved from the shared account to its own account was down for over 24 hours. I get the feeling that the delay was with Jodohost’s DNS servers not updating for some time after the change was made.

It looks like the only way to get around the problem of moving several domains from the shared account to their own accounts without their email going down for some considerable time is to have them hosted elsewhere. Then, if i have a mind to, to move them back to Jodohost after a few days.

or get a third party dns provider where we could instantly change the dns settings via IP.

correct me if I am wrong here

The DNS servers sync very regularly as in max time between sync being 2-4 minutes. DNS reort will typically help you knwo if the issue is with an ISP or on our servers. We can force hpshere to recreate DNS which helps in some cases, but not always. you would need to request this via ticket with the details for what is needing to be updated.