Irony helps us play!
Join Date: Jan 2006
Sportbike: 2000 F4
Years Riding: Long enough to know better
How you found us: some hot MILF whispered it in my ear
This can be caused by a few different reasons and it has to do with improper (or slightly slow/lagging) load balancing on the provider side, incorrect DNS TTL settings (with respect to bad load balancing techniques just mentioned - provider side), client caching DNS (not looking back up an IP for a domain name it previously looked up but instead using what it got previously - user side problem) or the client not respecting the TTLs (the record said I'm good for 5 seconds, but the client still uses the old info 30 seconds later and beyond - basically a restate of the previous - dns caching - user side problem) that are set on the domain record(s), bad page caching on the user side ( it thinks the error page is the real page, and continually pulls it up from local cache each time after encountering it once - client side problem). Or, a multiple combination of any of the above.
Last edited by Arch; 03-19-2011 at 08:40 AM.