DNSworks is looking for a technical cofounder. | Hacker News Reader

DNSworks is looking for a technical cofounder.

17 pointsdnsworks7 comments

Greetings!

We're DNSworks, and we're working on solving operations problems. DNS is the first peg in a large board. We're looking for a technical-cofounder to join our team. SOMA is our home, but we believe if someone is a good fit, they can be located anywhere within the same timezone.

What we'll offer

  - A significant equity stake
  - Caffeine, lots of it
  - An opportunity to make an impact on operations groups
  - Some compensation

What you bring to the table

  - A solid work ethic
  - A "Do No Harm" attitude
  - Expertise in Ruby & Ruby On Rails
  - Love of understanding how things work
  - You're not afraid of re-implementing protocols from RFCs         
  - You have a very strong understanding of TCP/IP

Here are some links to projects & papers that are really exciting to us. http://github.com/jpf/domdori | http://github.com/jpf/eventdns | http://tinydns.org/ | http://bind-dlz.sourceforge.net/ | http://en.wikipedia.org/wiki/Anycast | http://www.pch.net/technology/anycast.php | http://www.sanog.org/resources/sanog5-woody-anycast-v10.pdf | http://www.ietf.org/rfc/rfc3258.txt | http://www.quagga.net/ | http://www.bgp4.as/

We're not just a web start-up, we're building real infrastructure, the kind of fun technologies that keep enterprises afloat. If this excites you, then send a tweet to @dnsworks and let's get some coffee!

To anybody questioning what the next level of DNS could be, think of this way: infrastructure services like EC2 or Slicehost enable us to move/copy/build out images quite easily. But if this flexibility is not matched by API-driven networking surrounding our servers, there will always be a ceiling of flexibility that our servers cannot realize.

I don't quite know what dnsworks has in mind, but anything that aims to make DNS as flexible as other stuff is becoming, will be quite useful.

Related reading (not by me): http://perspectives.mvdirona.com/2009/12/19/NetworkingTheLas... http://www.bretpiatt.com/blog/2009/12/20/public-clouds-and-t... http://www.rationalsurvivability.com/blog/?p=1603

Can you be a bit more specific about what you're doing? DNS is a big field...

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!

Reply on news.ycombinator.com