[general_re]

The real problem is that some nameservers either cache negative results way longer than they should, or they simply don't respect the time-to-live for caching in the first place. It really depends on how often each individual nameserver is set to expire previous results and query the root servers once again. For some, that's as often as every four hours or so. For others...well, it could be several weeks before the "inactive" status is finally erased from the entire internet - it could be several weeks before the whole joint gets the inactive infomation, let alone the correction. That's why some people never have gotten knocked off yet - their DNS servers are/were still caching the old (but still valid) information, and hadn't (yet) been told to deactivate www.freerepublic.com. They may not ever get knocked off, if their DNS server doesn't query again until after the information is corrected anyway. Bottom line is there's no rhyme or reason to it - I'll still bet most people will be back up and running by tomorrow morning, but there's simply no way to know how long it will take to propagate everywhere.

[CedarDave]

Thanks for the explanation on why it will take so long to get everybody back on line. After this, I'll bet lots of folks will remember Freerepublic2 on Yahoo. (BTW, just doing a search on Yahoo for Freerepublic didn't get me to the site. Somewhere in my memory I brought up the "2" and got the message board.) Some bozo there thought it would be neat to post some anti-semitic crap and I emailed JimRob earlier this evening to delete it.

[quantim]

Something is amiss, still. I have bought domains and slapped up a welcome page with DNS propagation in 2-3 hours. It has been about 12 hours in Detroit, still not up.

BTW, I snagged www.ketchupboy.com anyone want it?