On Sat, 28 Dec 2019 22:39:05 +0100 Andreas Schwarz via nsd-users <[email protected]> wrote:
> On the "nsd-control addzone/delzone": it works a bit different from > defining zones in your configuration, just as the error message says. > > It is rather intended to be used with patterns. You configure a > pattern in your configuration, then you tell nsd via nsd-control > addzone to use a specific pattern for a specific zone. nsd keeps > track of these assignments in a file usually in > "/var/lib/nsd/zone.list" (configurable via "zonelistfile"). > > Zones can be added/removed pretty dynamically that way. What nsd does > internally when receiving the addzone/delzone I haven't cared about > so far. I'm not yet familiar with these patterns and the manpage is only comprehensible when you already understand it ;-) Anyway, I just tried a "nsd-control reconfig" and that rereads the zone file into memory. But I'll have a look at it tomorrow. It's time for a beer over here :-) > On the config in general: > "server-count" should be set to the number of CPUs of the respective > machine. And, if you have this set to more than 1 and run it on > Linux, you might also want to consider setting "reuseport" to "yes". > I have more experience with this option from a high performance > unbound system, but activating this option helped improve performance > by a margin of 30-40%. I think it has a similar impact on nsd when a > high amount of requests has to be served. This is a low level system with only a few hundred domains. I think one CPU will be sufficient. Thnx for your reply, R. -- richard lucassen http://contact.xaq.nl/ _______________________________________________ nsd-users mailing list [email protected] https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users
