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.
Luadns, managed DNS with Git and Lua scriptable back-end.
11–20 of 23 posts
Re: Luadns, managed DNS with Git and Lua scriptable back-end.
#12Will 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.
If you took notes on your setup I'd be very interested.
Re: Luadns, managed DNS with Git and Lua scriptable back-end.
#13Will 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.
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.
#14Any 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.
Re: Luadns, managed DNS with Git and Lua scriptable back-end.
#15After reading the title I was a little surprised when I skimmed the documentation. It seems like a better title would be: "Luadns, managed DNS with Git and Lua scriptable front-end " 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, t…
Who can make DNSSEC a requirement? How will it be enforced?
Re: Luadns, managed DNS with Git and Lua scriptable back-end.
#16After reading the title I was a little surprised when I skimmed the documentation. It seems like a better title would be: "Luadns, managed DNS with Git and Lua scriptable front-end " 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, t…
Who can make DNSSEC a requirement? How will it be enforced?
Any customer can make DNSSEC a requirement for adoption. Bob or Alice simply choose a different provider to enforce their requirement.
From a post downthread it is clear that the luadns team is well aware of how they will move forward in light of the tinydns feature set.
Re: Luadns, managed DNS with Git and Lua scriptable back-end.
#17My humble suggestions:
Your pricing page "Sign Up" buttons should go to a sign up screen not a sign in screen.
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?
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.
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).
Re: Luadns, managed DNS with Git and Lua scriptable back-end.
#18Any 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.
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.
Re: Luadns, managed DNS with Git and Lua scriptable back-end.
#19My humble suggestions: Your pricing page "Sign Up" buttons should go to a sign up screen not a sign in screen. 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 t…
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!
Re: Luadns, managed DNS with Git and Lua scriptable back-end.
#20Will 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.
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!?
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
btw, gdnsd dropped DNSCurve support in recent builds, so it's only curvedns now.