QUOTE(Julian @ Feb 25 2009, 06:27 AM)

For what it's worth, and this is probably more due to the time difference than anything else, I didn't even notice

went down until I saw
Mike's announcement of it.
Which speaks well of the promptness of your response,
Mike.
The site would have been down for you between about 4:30PM Monday and 4:30AM Tuesday. I became aware of the problem around 11:30AM Eastern (4:30PM your time), started working on it by 12:30PM, had the site up for testing by 10:00PM, and back open around 11:30PM.
QUOTE(Dontreadonme @ Feb 25 2009, 07:06 AM)

I'm currently in Okinawa and had the same situation as you did
Julian. No clue until this thread popped up.
This seems like an appropriate time to mention that if you love

and appreciate the hard work and dedication that
Mike and
Jaime put into this site, send a
donation to the support the cause!
I'm glad you weren't impacted.

And thanks for the donation plug... heh.
QUOTE(logophage @ Feb 25 2009, 03:59 PM)

I can confirm that this was a DNS issue. DNS changes do take a while to propagate. Some NAT routers cache DNS entries as well as your computer. In the past, I've explicitly purged my local DNS and my NAT router DNS entries to force an update more quickly. This doesn't help speed up your ISP's DNS updates, of course, but does eliminate some of the slowness.
Yeah, I have Comcast, and their DNS servers are painfully slow to update. The move was complicated by the fact that we have our own nameservers now. I had to register their hostnames before our registrar would allow me to set the nameservers for the domains to the new nameservers. It all happened very fast, though. I remember when DNS changes would actually take 48 hours to take effect... heh.
In any event, things seem to be running smooth on the new server. The site seems faster and more responsive in general. I am trying to give myself a crash-course in optimizing the server, and I think I have a pretty good grasp on what can be done to tweak the server to increase performance even further.
I'll be working on the issues listed above in the next two days or so.

Mike