Forum Moderators: phranque
I've read that google caches it's own DNS - this could mean we're not in the same place when google comes back!
Not 100% but I'd suggest that you run the risk of Google's cache not knowing the new IP when it does the crawl - their cache times are often talked about in terms of weeks so you could end up being unlucky...
Personally I think that dynamic IP's for websites are a total waste unless you can manage to consistently keep the same IP for weeks/months as well as ensuring the website maintains optimal uptime.
- Tony
<edit>Bad spelling</edit>
[edited by: Dreamquick at 3:54 pm (utc) on Mar. 26, 2003]
1) Google DNS caches are expressed in terms of weeks - DynDNS may have a method of shortening this but I wouldn't like to say.
Also see this post which talks about DNS TTLs which are the root of your woes;
[webmasterworld.com...]
Google KB;
[webmasterworld.com...]
2) Connection - specifically how long you can keep a single IP and how long you can keep the machine running. Changing IP too often or not having the machine alive when someone machines a request are going to kill your chances of getting crawled.
In all honesty Brett may use DynDNS but since he's a professional I'd wager he has a nice little setup which either has a static IP or possibly a dynamic IP which can be retained indefinitely - which is where using DynDNS really makes sense.
Since you haven't said what type of configuration you are running it with there are a number of factors which stop me giving an absolute answer.
For a more focused version of dynamic donnection issues try here;
[webmasterworld.com...]
...oh yes and site search is your friend!
- Tony