Absolutely. The first product we're building is a managed, authoritative DNS service on a highly redundant global network, with a great RESTful API and a low-cost, metered billing. After that's launched, we plan on adding some enterprise features like strong usage and routing analytics, and maybe some DIY CDN functionality. We're also thinking through a number of white-label features for the hosting market.

Likely much to Paul Vixie's chagrin, we're looking at DNS as a good platform for building low-latency, geographically specific services.

I love infrastructure-as-a-metered-service in general, but how do you expect to get any significant revenue from authoritative DNS? Even big sites have relatively trivial needs.

we're looking at DNS as a good platform for building low-latency, geographically specific services

Hmm. Weather reports over DNS? :-)

The problem I'm solving is not about volume, but rather a value proposition. There is value in reducing the number of operations problems that a company needs to solve.

DNS as a platform isn't really about serving content, but providing data for applications to use when making decisions.

@dnsworks - you should chat with @jf (twitter)/(jpf on github) and/or Jeff Lindsay. They've got some pretty awesome ideas for DNS beyond traditional use.

Brian, thanks for the advice. I actually sat down with @progrium (Jeff) a few weeks ago. Really, really smart guy, and the work that him & @jf have done so far with Domdori & EventDNS is awesome!