News

Service outage

Oof, well that sucked. The hardware that StaticCling runs on suffered a large failure, and it knocked us out for a couple of days -- this is actually the longest outage we've experienced in the 15 years the service has been up.

The good news is no data was lost, and we've been furiously moving things around to get our service restored. We've migrated to DigitalOcean, which should also provide for easier future scaling, if that's ever a concern. (Please click that link if you might want some DigitalOcean VPS, it saves StaticCling $$$!)

We're still bringing up various internal services (email, etc), but the core DNS service and API is back in action.

Whoa! Upgrade time!

It's been... well, a really long time coming, but it's finally here!
We've pushed a pretty substantial update -- actually, more of a total rewrite.

StaticCling has been in constant service since 2001, and it certainly
started feeling like it was written around the turn of the century.
This rewrite provides a (much needed) modernized backend that should
scale upwards well, along with a full API to encourage rapid
development of native clients.

All the basic features are still there, plus we've added:

Subdomain support (you can have many records attached to one account)

DNS load balancing

Full NS delegation (if you run your own nameserver and want ultimate control)

Old clients that use the original challenge/response setup are no longer
supported. (There is practically no one using that, unfortunately.)
Nearly everyone is using the original, simplistic and insecure URL
format. For this transition, that format will continue to work
temporarily. Please update your client if you're using one on a timer
(cron or whatever.) We'll disable all the legacy stuff in the next
couple of months.

You can find a new command line client
here.
It will run on any system that can run Ruby.

Enjoy the new setup, and let me know how it works for you. Thanks for using StaticCling!