moving web host with own nameservers without downtime

Hi,

We have 20 clients whose websites and e-mail we host on shared hosting.  Everyone uses these settings:

nameservers: ns1.compubase.ie, ns2.compubase.ie
POP: pop.compubase.ie
SMTP: smtp.compubase.ie
FTP: ftp.compubase.ie

We need to move to a completely different web host, probably to a dedicated VS or similar.  Obviously, I will need to copy everyone's website to a local PC, then migrate to the new server and I will need to recreate everyone's mailboxes.  If possible, I want everyone to still use the same compubase.ie POP, SMTP and FTP addresses (and not to have to change nameservers for their domains).  But given that we're using our own nameservers, managed by our current host, what is a good strategy for moving to a new host without any (or much) downtime?

Thanks in advance
mark_D74Asked:
Who is Participating?
 
shalomcConnect With a Mentor CTOCommented:
the trick to do is to lower the TTL on all of the services you are about to modify.
You intend to keep all the services names and only to modify their IP addresses, so your only problem is the period of time when the name servers and the end points (PCs, servers, etc) are caching the resolved IP addresses. That's what lowering TTL is supposed to help with.
If your current TTL is a day (86400 seconds) then lower it to a something like 300 seconds a day before moving, do the change, wait a day, and raise it again to a sensible number like its previous value.
Your support staff should be familiar with the "ipconfig /flushdns" command.
0
 
shalomcCTOCommented:
Is compubase.ie your owned domain, or does it belong to the hosting provider?
0
 
mark_D74Author Commented:
compubase.ie is our own domain
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.