vitalie

Yes, I'm using net/http.

I rewrote my DNS checking tool (http://www.dnsinspect.com/) in Go and I saw huge differences in resource usage (previously it was implemented with Ruby on Rails + EventMachine), my memory usage went down from 128MB per background worker to a few KB.

Now I'm able to run hundreds to thousands of concurrent reports using a small VPS, the Go application is using 36MB of RAM (24MB front end + 12MB for background workers). Go language is well suited for my particular case (many concurrent IO operations).

This was my first Go project, in a week I was comfortable with it, I had many alternatives but I really liked the simplicity of Go, fast compilation and easy of deployment. Because I've missed some pieces from the Ruby's world I've combined Jekyll (Compass, HAML SASS, RedCarpet, etc) with Go. :)

AXFR support is ready, check slave function from the manual:

http://www.luadns.com/help.html#functions

At this moment we have no plans to adopt DNSCurve, but if we'll see more and more demands we may change our plans accordingly.

Indeed, free users are notified to upgrade their account upon hitting quota.

We are not collecting CC information as we chose Avangate to process our orders. Dealing with CC it's a big hassle, we wanted to allocate more time for the service itself, maybe in the future it will make more sense.

Thank you for your suggestions!

AXFR support it's on our priority list, we'll release an update soon. Please, subscribe to our Twitter feed or Blog's RSS feed and we'll make an announcement when it's ready.

Yes, it's a young service, we have launched on February 10 (in production since December 15) and we are aware of great responsibility involved by this service. We took many measures to ensure quality of this service. All servers and services are monitored with Nagios and we are notified by email and SMS. We are adepts of test-driven development, so everything it's tested before released in production.

Thank you for your suggestions!

We are trying to avoid reinventing the wheel. :) TinyDNS served me well more than 10 years, I like the design of this piece of software ( although it needs 2 pairs of glasses to read it :) ), so it was a natural choice.

To provide IPv6 and DNSSEC support we'll provide another set of name servers with NSD/PowerDNS as we designed Luadns with flexibility in mind (it's already 100% compatible with PowerDNS).

Yes, we have support for wildcard records. Example:

https://github.com/luadns/zones/blob/master/example.net.lua

Hello,

I'm Vitalie Cherpec, the founder of the Luadns project. :)

@relix It's a design choice, Lua code is used only to generate records. Executing user code on each lookup it's just too dangerous.

We wanted fast lookups and security. User code is executed in a restricted Lua environment in background.

If we'll have enough requests we'll add special functions to handle geo-aware DNS load balancing.

Same problem with wikileaks.ch domain, no answer from EveryDNS's nameservers:

http://www.dnsvalidation.com/wikileaks.ch http://www.dnsvalidation.com/wikileaks.org