I recently had to change the IP of one of my sites that runs on my server. When the change was first made, for about 30 minutes or so, anyone coming to the site was ending up at another one of the sites on the server.. but after that, everyone is now making it to the new IP.. The only problem is that after 4 days, the Yahoo bots/crawlers are still going to the old IP, which is resulting in page-not-found errors on the wrong site/domain (old IP).. I reported it to Yahoo and they said it's just a matter of time for the DNS to update.. So, how long should this type of change take to replicate? and why is it that in 4 days, ~90,000 visitors, other bots, etc, can all seem to find the correct IP, yet Yahoo can't ?
Uhh.. that's the problem.. it's TRYING to crawl it, but it's going to the old IP, and trying to crawl URLs there, which is another domain/site..
Did you try to ping your ip and see which ip its showing new or old. Yahooo results arent updated regularly i guess ull have to wait
And this is why you should always set your DNS TTL as low as possible and feasible (600 - 3600). Makes quick changeovers faster, easier and has less complications. With Yahoo's response, I'd say all you can do is wait and hope it fixes itself.
DNS TTL was set low, and as posted, after less than an hour or so, every person, bot, crawler, scrapper and spammer on the planet was finding the new ip/site just fine, EXCEPT for the Yahoo bots.. anyway, after 6 days the Yahoo crawlers have finally found their way to the new IP.
actually you made a small mistake here, But do remember This from next time. DNS updates can take upto a week to be updated around the world, but generally 90% of visitors get updated within 72hours of change.Whenever you are moving your site and IP address changes, you should never remove the site from old server. keep it running parallel to new server. if you have a dynamic content type site, then you should disable adding new content on old server to maintain database consistency. also put a small note about migration saying visitors to clear their dns cache or visit site by IP address for time being while dns caching on. This way you won't loose any traffic.
yeah, thanks.. problem is we weren't "moving" the site to a new server, just a new IP on the same server.. Not sure how easy it would have been to keep it running parallel on both IP's in the same server. at any rate, since Yahoo was the ONLY one in the entire world that had the issue, it would not have been worth the trouble..