Hello,
I'm involved in a project that needs to remote control a NSD server.
Since NSD3 has no remote control functionality and NSD4 will, I see a
few possibilities to accomplish this:
1. Since the project is still in the early stages, simply waiting for
NSD4 to be released is an option. My question in this case is:
* Is there an estimate of when will NSD4 be released? Obviously no
one can commit to a date,
but is the time left before release measured in weeks, months, or
years?
2. Backport the remote control functionality from NSD4 to NSD3. My C is
rusty, but I'm willing to put in the effort. My questions in this case are:
* Is this technically feasible? If remote control is tightly
integrated into NSD4,
it may be futile to try to backport it.
* Does this make sense time-wise? If NSD4 will be released before
backporting is done,
there's no point in backporting.
3. Write my own script that accepts commands over the network, modifies
nsd.conf and/or the zonefiles, and SIGHUPs the NSD daemon. This is the
"default" if 1 and 2 are impossible. It could also be a stopgap
measure
until NSD4 is released.
Cheers!
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20131003/4aefcad8/attachment.htm>
On 03/10/2013 23:22, Artom Lifshitz wrote: Hi Artom, [...]> 3. Write my own script that accepts commands over the network, modifies > nsd.conf and/or the zonefiles, and SIGHUPs the NSD daemon. This is the > "default" if 1 and 2 are impossible. It could also be a stopgap measure > until NSD4 is released.I don't presume to speak for the NSD developers, but I know that NSD4 is in a good state. I have been testing the beta releases, and am quite satisfied with them. I know some sites are even using it on production servers. I suspect and hope that there will be a proper release real soon now. If I were you, I'd just write some scripts to work with NSD3 for now, and upgrade to NSD4 when it comes out. Don't waste effort back-porting NSD4's remote control into NSD3. It will be more work than you might imagine. Regards, Anand
Hi Artom, On 10/03/2013 11:22 PM, Artom Lifshitz wrote:> Hello, > > I'm involved in a project that needs to remote control a NSD server. > Since NSD3 has no remote control functionality and NSD4 will, I see a > few possibilities to accomplish this: > > 1. Since the project is still in the early stages, simply waiting for > NSD4 to be released is an option. My question in this case is: > > * Is there an estimate of when will NSD4 be released? Obviously no > one can commit to a date, > but is the time left before release measured in weeks, months, or > years?We are very close towards the NSD4 release. At the moment we are finalizing code review. If that is done, we are releasing a candidate. So the actual NSD4 release, I would say it is a matter of weeks. Best regards, Matthijs> > 2. Backport the remote control functionality from NSD4 to NSD3. My C is > rusty, but I'm willing to put in the effort. My questions in this case are: > > * Is this technically feasible? If remote control is tightly > integrated into NSD4, > it may be futile to try to backport it. > > * Does this make sense time-wise? If NSD4 will be released before > backporting is done, > there's no point in backporting. > > 3. Write my own script that accepts commands over the network, modifies > nsd.conf and/or the zonefiles, and SIGHUPs the NSD daemon. This is the > "default" if 1 and 2 are impossible. It could also be a stopgap measure > until NSD4 is released. > > Cheers! > > > _______________________________________________ > nsd-users mailing list > nsd-users at NLnetLabs.nl > http://open.nlnetlabs.nl/mailman/listinfo/nsd-users >