News for hackers. Stuff that matters.
Re:Luadns, managed DNS with Git and Lua scriptable back-end. by zdw on Tuesday April 03, 2012 @08:49PM (#3795608)
Will you support DNSCurve? It would be nice to get more people on that particular bandwagon.

I set up a git/rake/djbdns/curvedns setup in an afternoon with a few VPS's, which has been quite solid for me.

Re:Luadns, managed DNS with Git and Lua scriptable back-end. by jevinskie on Tuesday April 03, 2012 @09:23PM (#3795720)
How has curvedns been for you? I need DNSCurve for a research project of mine but I'm very frightened to see that curvedns is the only forwarding implementation and gdnsd is the only authoritative implementation. Speaking of implementations, what the heck do you use for a client/resolver!?
Re:Luadns, managed DNS with Git and Lua scriptable back-end. by zdw on Wednesday April 04, 2012 @09:39AM (#3797491)
That's the chicken/egg problem. The only real clients I've seen right now are the python testing implementation, OpenDNS's servers, and the DNSCrypt implementation that OpenDNS released: http://www.opendns.com/technology/dnscrypt/

Looking at one of my CurveDNS logs for the last few days and doing some very basic math:

    $ grep "query too small to be DNSCurve packet" *.s | wc -l
    27539

    $ grep "DNSCurve shared secret" *.s | wc -l
    2282

    2282/29821 = .07652
So about 7.6% of all DNS queries are being answered via DNSCurve. Doing reverse IP lookups on the querying servers, nearly all of these requests are coming from OpenDNS.

btw, gdnsd dropped DNSCurve support in recent builds, so it's only curvedns now.

Re:Luadns, managed DNS with Git and Lua scriptable back-end. by vitalie on Wednesday April 04, 2012 @11:12AM (#3797932)
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.
Re:Luadns, managed DNS with Git and Lua scriptable back-end. by sigil on Tuesday April 03, 2012 @09:05PM (#3795664)
If you took notes on your setup I'd be very interested.