GoDaddy Bobbles DST Changeover?
Several readers alerted us to this piece in PC World reporting on concerns that GoDaddy might not be ready for the DST changeover. Some readers, and others, claimed that GoDaddy's servers are not reachable now and are not serving email or web sites; but others see no evidence of this. The article recounts the rather flip response one GoDaddy customer got from their tech support: "As Daylight Savings [sic] does not apply to our servers, since we are on Arizona Time and our time zone does not change, our servers wouldn't update." When IDG News Service contacted GoDaddy they got an altogether more sensible reply.
For international services like domain registrars, switch to UTC already. Running the server on a local timezone will only lead to confusion.
All my internet servers just use UTC. NTP synchronized, naturally.
Oolite: Elite-like game. For Mac, Linux and Windows
I dont understand, all that godaddy does is manage dns, web servers for parking space and basic MX services. How can someone fuck up with this kind of setup? Even if DST patches are off the only problem that i see is with
1. DNS TTLs being incorrect.
2. Your mail showing incorrect time
3. Web server logs (who analyzes these anyway) showing an incorrect time.
How can any or all of these bring down a site. WTF?
Microsoft: "You've got questions. We've got dancing paperclips."
The real question is, is the problem DST related, or is it a coincidence?
;-)
Sure, it happened around the day of the change. Sure, they were pretty flip about responding to peoples' questions about their DST change readyness. But is it fair to jump to the conclusion that it [the outage] is because of the new DST rules? It could be that they are incompetent in other ways.
--Xandu
Remember IntellAdmin, offering a free DST patch for Windows 2000? Well, it doesn't work. I installed it on a Win2K system, and the time didn't change to DST. I contacted Intelladmin, and got "workaround instructions" (open clock, change to another time zone, change back, then reset the clock to the correct time.). It only changes to DST the next time you manually set the clock.
So if you deployed this "patch" on your Win2K machines in a corporate environment, the time is going to be wrong when everybody shows up on Monday.
I swore it said GoDaddy Boobies Changeover.
James Tiberius Kirk: "Spock, the women on your planet are logical. No other planet in the galaxy can make that claim."
And to think that some people claim Linux isn't ready for the desktop! ;)