Forum Moderators: open
If possible, try to keep both the old and new host up to date until the DNS changes have propagated throughout the net, that will probably be at least some days are the changes are done.
René.
Google maintains their own dns info and it seems to lag behind a little. So don't be surprised if googlebot comes a calling to the old ip.
If the old host shuts down with very, very little notice, there's a small chance that you could fall bewteen the cracks for a month, maybe 2. Hope you make it.
Good luck,
rmjvol
Regarding this subject matter, I wonder how many email inquiries are generated into corporate headquarters regarding this issue. I've noticed that it seems to be a major concern when companies decide to switch to new hosting providers.
I wonder how feasible and useful it would be to create an online tool to allow companies to submit requests to update their Google DNS information. This way, companies can proactively notify Google of the DNS change when they move to a new hosting provider, and could potentially cut down on the number of "help" emails sent to Google.
Just a thought I had.
My experience: I moved to a new host, put up an .htaccess file with 301 permanent redirects at the old host and googlbot was at the new host crawling two days later.
That said, if the deep crawl is done on your old host, then the host shuts down (without enough time to keep an .htacacess there) you may lose out for awhile.