Luadns, managed DNS with Git and Lua scriptable back-end.

The Lua-code doesn't appear to be executed once for each lookup - as I first imagined how it would work. So sadly, one cannot point different region users to the closest server IP.

After reading the title I was a little surprised when I skimmed the documentation. It seems like a better title would be:<p>"Luadns, managed DNS with Git and Lua scriptable <i>front-end</i>"<p>It seems like tinydns is your back-end. Which in my opinion is nothing to be ashamed of. When I thought the service was a new dns server written in Lua I was less intrigued. There are a ton of pitfalls when writing your own dns daemon, tinydns is a good choice.<p>What are you going to do when dnssec becomes a requirement?

History: (from <a href="http://www.luadns.com/about.html" rel="nofollow">http://www.luadns.com/about.html</a>)<p><i>I was a happy user of a free DNS hosting service for many years, when this service was acquired by a competitor in august 2011, I was forced to move somewhere else.<p>While migrating my zone files I realized that I don't like Bind syntax files neither administering tens of domains through a web interface. I've started to experiment on how it should look a perfect DNS service for me. I've realized that I would love to store my configuration files in a Git repository and I would need some configuration language for templating (Lua).<p>This is how Luadns was born on October, 2011.</i><p>I don't know if this is an after the fact explanation, but either way it's a very good story about scratching your own itch.<p>By the way, they had me at <i>I would love to store my configuration files in a Git repository</i>. As soon as I have a use for this in a new project, I'll be their user. The examples are pretty cool too.

Will you support DNSCurve? It would be nice to get more people on that particular bandwagon.<p>I set up a git/rake/djbdns/curvedns setup in an afternoon with a few VPS's, which has been quite solid for me.

My humble suggestions:<p>Your pricing page "Sign Up" buttons should go to a sign up screen not a sign in screen.<p>On sign up you should collect credit card information. You will get less sign ups but more revenue, and you won't have to shut off free people if they go over their query quota. Auto upgrade if they do? Send an e-mail saying they are close to meeting their query quota and that they will be auto upgraded if they do?<p>After sign up you should display a message saying for them to open their e-mail client and click the confirm e-mail - not just a login screen.<p>Kill the $39 price point. Just have $9, $27, $69 and then below those three have the free option, and explain if they go over their quota they will be upgraded (thus requiring cc information on their account).

Any chance of you guys allowing AXFR transfers? I really like the ideas behind the service, however, I have reservations about moving production DNS given your relatively young age. Being able to have secondary DNS elsewhere eliminates the risk of switching over but maintains all the upside of your excellent interface.