4 ms·
Brilliant in its simplicity. Could you share the technical details? What DNS server/software are you using? How do you handle input, errors (broken zones? do y
by spindritf 14y ago
Brilliant in its simplicity.
Could you share the technical details? What DNS server/software are you using? How do you handle input, errors (broken zones? do you perform sanity checks?), and reloads?
Do you enforce any limits? Support DNSSEC?
What's the web stack?
- Amfy 14y agoI'm glad to answer your questions. As I wrote, this was just a fun project for like two (maybe three) evenings, you can't expect to much. Webstack is Nginx + Ruby + Sinatra + MySQL (Datamapper, I know I should switch to Sequel) and a worker in Node.js on the slave nameserver for writing configs + reloading nsd Servers are two small VPS, one on my own dedicated server in Frankfurt, Germany, the other in Canada from lfchosting. Nameserver is nsd, because it looked not to bad. > How do you handle input, errors (broken zones? do you perform sanity checks?), and reloads? I'm performing some checks, with nsd-checkconf, etc, but I'm sure there is something I could improve. It gets reloaded everytime someone enters a domain name or pushes changes to bitbucket/githup and they are posting to the specific URL. > Do you enforce any limits? Support DNSSEC? Nah, there are no limits, currently. DNSSEC: No, also not looking to implement it with this project, since besides that I'm working on a more serious one, even with anycast, etc and there is dnssec already possible. I hope I was able to answer your questions as you expected it, please let me know if you want anything more detailed or have more questions for me :)