The only issue (unless you take steps to mitigate it) is that for a period, some users, including search engine spiders, may be unable to find your site because of "DNS Caching".
When an IP address is looked up by a DNS server, one of the parameters that is returned is a Time To Live value (TTL), sometimes called "Minimum". This value tells the requesting DNS server how long it can hang on to the result for in order to save repeated requests to the authority DNS servers for your domain (the ones listed in your "whois" record).
Now, this value can be anything from nothing to weeks; so what effect an IP address change has on your users depends on:
a) What is it now?
If it is zero, there is no problem. Change your IP address and away you go. If it is not zero, then:
b) Can you change it?
If you can't change it, there's not a lot you can do. Go ahead and make the change and accept that there is the possibility that, for whatever period it is currently set to, that a few users may experience an outage.
If you can change it, then:
c) Can you wait for at least the current setting before changing IP?
If you can, then simply set it to zero, wait for whatever it was set to before, and then change your IP. Then you can set it back to a higher value to avoid unnecessary load on your authority server.
With regards to the situation with search engines and what happens when a spider gets a 404, I don't think there is a definitive answer. In my experience, Google at least is extremely forgiving. Pages certainly aren't dropped at the first whif of a 404 or server outage. I've got pages still indexed in Google that haven't been online for over 15 months!
Hope this helps!
Last edited by dmorison; 18-10-05 at 07:16 PM..
|