Viewing profile — supine

An example of some of the pitfalls involved: http://search.cpan.org/~drolsky/DateTime-1.10/lib/DateTime.p...

...and just when you thought it was safe to go back outside leap seconds rear their ugly head and ruin your day.

I think you just made a better case for having everything in UTC. Instead of having to remember multiple offsets, one for each location, you just need to know your current offset t…

Pointing out weird correlations that have absolutely no causal link whatsoever is a global sport. https://www.google.com/search?q=weird+correlations The first result is a beauty ht…

The concept of "everyone on support" is practiced in a lot of orgs, with varying implmentations (e.g. "one whole day a month", "one whole week per quarter", "one week of half days …

No, this is for domains where .worldnic.com is the authorative server. If you registered your name through NetSol but hosted the DNS servers elsewhere then you would just be relyin…

If your name servers are *.worldnic.com it appears you are affected. First mention on Twitter was an hour ago https://twitter.com/thefrost/status/357483942082920449

a.ns13.net. and b.ns13.net. were the last 2 to be fixed, seems to be all ok now. If you can, flush your resolver cache.

Some of those that were broken are starting to work again. However the NXDOMAIN responses will have been cached and take a little while to expire.

They have 7 name servers, 5 are broken and returning NXDOMAIN for all domains. Working: b.nic.io. ns1.communitydns.net. Not working: a.nic.io. a.ns13.net. b.nic.ac. b.ns13.net. ns3…

And it's gone... 404. Google cache: http://webcache.googleusercontent.com/search?q=cache:MRYAvjI...