Thanks, I'll keep that in mind.
Any idea what causes the problem in the cache?
And, while we're at it, why can I get back on the site without doing anything at a later date? This just happened to me last Sunday morning again.
I may need to purchase the services of additional backup DNS servers, but I'm moving a god-awful number of domains around right now and will better be able to access DNS issues once all the changes settle.
DNS is a distributed database with propagating caches and other DNS servers need to cache all the new information for the sites I'm moving before I can ascertain the load.
It may be a bit hectic for a week or two.
Thanks, will try to allay consternations that come up... not that anyone will listen to non-tecca.
Craven de Kere wrote:I may need to purchase the services of additional backup DNS servers, but I'm moving a god-awful number of domains around right now and will better be able to access DNS issues once all the changes settle.
DNS is a distributed database with propagating caches and other DNS servers need to cache all the new information for the sites I'm moving before I can ascertain the load.
It may be a bit hectic for a week or two.
Ah, thank you for the explanation, Craven. This makes some sense to me.
