DNS data is cached all over the place, and Google even seems to run their own extra chache. Typically it will take about a week until all normal users see the new IP, for search engines with custom caching it may take longer than that (eg. a month).
I had the same Problem last month. Ich cahnged the IP for a domain. A week later nearly all the surfer used the new IP. The freshbot used the old IP. Then the Google IP cache was updated before the deepcrawler started his monthly crawl. Now all is ok.
Well for me it took almost ten days. I kept the site at both places, and now its all good :) My site gets refreshed daily
So, I simply have to wait until Google finally dumps my old IP and start spidering my new IP before letting go the old site, right?
How can I be sure of that?
>>So, I simply have to wait until Google finally dumps my old IP and start spidering my new IP before letting go the old site, right? <<
No. If your dns resolves to your new host, dump the old one, if you wait for the googlebot, you may incur a duplicate content penalty.
I moved my site last Sun and on Monday afternoon googlebot was deep crawling the new IP. Funny thing though, she is still going back to the old host once or twice a day - same bots as already went to the new one. Hopefully she is just checkign that I really moved!
Check your logs at both hosts to see when the crawlers and users stop using the old one.
I thought 'duplicate content penalty' only hits sites which have the same content across different domains. Since Google only recognizes my old IP, and will only spider one site at a time, would you still consider my solution of 'waiting' as a potential problem? I just want to make sure everything goes fine. Thank you for your time.
>>and Google spidered the my old site<<
I assume it's the same site on a different ip, if thats the case, it's been spidered and all traffic will resolve. I was just erring on the side of safety, I know there are dupe filters, just don't want you to inadvertently get caught in one.
>> I assume it's the same site on a different ip <<
Yes! But Google spidered the OLD IP... New IP has yet to be visited by a Google spider.
>> if thats the case, it's been spidered and all traffic will resolve <<
Could you explain what this means?
>> I was just erring on the side of safety, I know there are dupe filters, just don't want you to inadvertently get caught in one. <<
I appreciate your concern. I don't really think this would trigger any alarms as I really don't have 2 domain sites running at the same time with exact same content. When Google refresh the DNS, it won't even see the OLD IP site.
But the question is when Google will finally recognize my NEW IP.