Jul. 17, 2025 13:19:14 Tyler Amick <[email protected]>: > On 7/17/25 10:56 AM, Nicholas Niro wrote: >> This is quite an interesting alternative indeed. But I can't help but wonder >> : If busybox dnsd worked correctly, would you have opted to use it instead? > > I'll be honest here, I likely would not. dnsmasq is very very well supported > and is running everywhere. If you have an integrated router/firewall, it's > likely running dnsmasq (both in consumer-grade and commerical-grade gear), > whereas I haven't seen any usage of bb dnsd in the wild. (Not to say it's a > bad piece of software, just that it's not very widely adopted.) > > Additionally, I've found that the integration between DHCP/DNS is > game-changing/indispensable. It's very nice to have any device that hops onto > the network become instantly resolvable by name without any user intervention.
You know, you made me realize that this could be implemented in bb dnsd too if the process would be made to re-read the config file when a HUP signal is catched. If this is not already implemented, I think this would make bb dnsd vastly more interesting. At this point it would just be a matter of calling a script when a new client is assigned an IP by the dhcp server. > > To each their own though. While I think dnsmasq would do better for your > application, I definitely understand the desire to use the tools you already > have installed. I do get what you're going for with the patch though, and I > encourage you try to get it merged. > > Regards, > -- > Tyler Amick > PGP Fingerprint: 8EAC 2FB2 21A3 98DE 7A19 EE0E 63BF 906B 9FCB B6F1 > PGP Public Key: > https://keys.openpgp.org/vks/v1/by-fingerprint/8EAC2FB221A398DE7A19EE0E63BF906B9FCBB6F1
_______________________________________________ busybox mailing list [email protected] https://lists.busybox.net/mailman/listinfo/busybox
