19 ms·
> Basically "DNS for impatient homelabbers/SMB's who don't want to have to learn how to write zonefiles and don't want some crazy enterprise omnibus thing eithe
by justinclift 6y ago
> Basically "DNS for impatient homelabbers/SMB's who don't want to have to learn how to write zonefiles and don't want some crazy enterprise omnibus thing either".
Dnsmasq or PowerDNS weren't suitable?
- cashewchoo 6y agoWorkable but no, not suitable. PowerDNS has a lot of features and isn't terrifically simple to deploy. DNSMasq is easier to deploy, but still has a lot of features and isn't easy to configure. The niche I'm aiming for is for people who just want to map hostnames to IP addresses. And note this isn't a commercial offering, just something I built for myself that I'm going to put up a website for and maybe some other people will find interesting. I do think I have some product-market fit because even among my dev friends, who are all quite talented, many of them have mentioned to me "yeah I threw bind9 on a server but decided I didn't hate typing IPs enough to actually set up and operate it". I'm aiming for zero onboarding time and zero maintenance headache. You run a docker container, map the ports, and then there's a nice web UI that takes you the rest of the way.
- justinclift 6y agoNo worries, that does sound useful. :)
- birdiesanders 6y agoTry running 15k containers, dnsmasq and powerdns fall over pretty fast. I have to run a BIND cluster of 3 machines to support the days when I am running at-scale testing of software (low load, but high instance count is a better fit for my work these days). I use 4th gen i7 machines as DNS resolver/caching servers, and using dnsmasq on the same machines I start to have issues around 400 clients, massive latency, broken responses, tons of crazy stuff. One BIND instance and I can get to about 7500 clients before it starts to get squeezed. The difference is huge in other ways, though. Configuration, operations, and maintenance of the BIND cluster is 20 fold more involved, and when things break, they can break in really confusing ways. Such is the world of computing though, the better something performs, the more places it has where you can mess it up.
- mdekkers 6y ago> [...] powerdns fall over pretty fast If you are running a properly configured PowerDNS, and 15k containers make it fall over, you don't have a properly configured PowerDNS
- justinclift 6y ago> Try running 15k containers ... That sounds pretty different from the audience they said they're targeting → "impatient homelabbers/SMB". As another commenter points out though, the load you're talking about definitely sounds like something PowerDNS should handle without much problem. Given reasonably spec-ed, hardware and software that is. It's used by some pretty big places: https://www.powerdns.com/users.html https://www.powerdns.com/users.html