nsd users - May 2019 - ?==?utf-8?q? ?==?utf-8?q? adding/removing slave zones

@Kaulkwappe: I do this for primary zones. But I could not get it to work with
secondary zones.
It would probably work, if all my secondary zones had the same primary
nameservers, which I could then configure in a pattern.
Unfortunately, the zones use a varying bunch of nameservers. Therefore from my
point of view, I would end up configuring a pattern for each zone. To reload the
pattern I would again have to use 'reconfig' option.

@Anand: no it is not causing any problems so far. It only feels rough compared
to primary zones with the 'nsd-control addzone' or 'nsd-control
reload' commands.
And if something feels rough, I usually asume that I am working against a system
and that there is a better way.



Thank you for your feedback.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20190529/62aa890b/attachment.htm>

On 29/05/2019 18:59, Andreas Schwarz wrote:

Hi Andreas,
> @Anand: no it is not causing any problems so far. It only feels rough
compared to primary zones with the 'nsd-control addzone' or
'nsd-control reload' commands.
> And if something feels rough, I usually asume that I am working against a
system and that there is a better way.
Given your use-case, I can't think of a better way of doing this. I
think your solution is just fine. Nothing rough or inelegant about it.
We do something similar for one class of zones we manage, except that we
generate a single file with all the zones in it, and then reconfig nsd.

Regards,
Anand