Luadns, managed DNS with Git and Lua scriptable back-end.
1–10 of 23 posts
Re: Luadns, managed DNS with Git and Lua scriptable back-end.
#2The 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.
Re: Luadns, managed DNS with Git and Lua scriptable back-end.
#3History: (from http://www.luadns.com/about.html)
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.
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).
This is how Luadns was born on October, 2011.
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.
By the way, they had me at I would love to store my configuration files in a Git repository. As soon as I have a use for this in a new project, I'll be their user. The examples are pretty cool too.
Re: Luadns, managed DNS with Git and Lua scriptable back-end.
#4The 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.
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.
Re: Luadns, managed DNS with Git and Lua scriptable back-end.
#5History: (from http://www.luadns.com/about.html ) 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. 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 se…
The dates line up. August 2011 was when Dyn bought EveryDNS and fucked everyone.
I have been helping people move off the Dyn platform and encouraging the development of efforts like this (both technically and financially) ever since.
Re: Luadns, managed DNS with Git and Lua scriptable back-end.
#6The 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.
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.
Do wildcard records work?
Re: Luadns, managed DNS with Git and Lua scriptable back-end.
#7After 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, tinydns is a good choice.
What are you going to do when dnssec becomes a requirement?
Re: Luadns, managed DNS with Git and Lua scriptable back-end.
#8Earlier quoted context omitted.
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.
Do wildcard records work?
Yes, we have support for wildcard records. Example:
Re: Luadns, managed DNS with Git and Lua scriptable back-end.
#9After 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…
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).
Re: Luadns, managed DNS with Git and Lua scriptable back-end.
#10After 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…
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% compati…
That's awesome. Do you mention that on your site? I don't remeber seeing it but I might have not looked for ipv6/dnssec after seeing tinydns.
Knowing the path forward includes ipv6/dnssec definitely makes me more willing to signup...