4 ms·
I assume you're using your shared host's DNS servers and that a move to a VPS also requires a DNS move. If it's possible to keep the same nameservers it's just
by jm4 18y ago
I assume you're using your shared host's DNS servers and that a move to a VPS also requires a DNS move. If it's possible to keep the same nameservers it's just a matter of changing the record and everything will work right away.
Switching nameservers is what takes a long time.
It can take 24 hours, but it's usually much faster. There have been times that I've seen the change take place in just a few minutes, but that only means that the nameservers I'm using have picked up the change. Other nameservers may take longer. The result is that you're not dealing with a total outtage. Some users will get pointed to the new location while others will get pointed to the old one.
You obviously want to do this when you expect usage to be at it's lowest and it wouldn't be a bad idea to have a message on the old site letting users know what's going on.
Also, as long as you're moving it's probably worth looking into a more permanent DNS solution so that you don't need to switch nameservers again next time you switch hosts.
- maw 18y agoIf you know you need to make to your network, you can set TTLs to be lower, several days in advance. Problem solved. (It's true that some crappy DNS resolvers don't honor TTLs, so you'll need to retain control of old servers for at least several days afterwards, to set up some automagic forwarding, receive mail from senders who haven't caught up with new MX records, etc. But none of this should be too difficult.)
- brk 18y agoTrue, but if you have a reasonably popular site SOMEONE has always broken DNS TTL's along the way. I've been through this more times than I can count... If your site is still small/early, it's less of an issue.
- maw 18y agoRight. So, like I said, you need to control the old servers for at least a few days after the cutoff date.