NSD 4.1.7 in EPEL

NSD
1

Dear NSD users,

Note that Paul wouters has pushed NSD 4.1.7 packages into the EPEL
repository for Redhat Linux and CentOS. Previously there was only NSD
version 3 in EPEL.

If you've got EPEL configured on your Redhat/CentOS systems, be aware
that you're suddenly going to get upgraded to NSD 4.1.7. This is a
major update, so you'll want to review your configuration for any
anomalies or discrepancies and so on.

Regards,
Anand

2

If your config is modified from the default, it will not replace it.
So provided nsd3 and nsd4 are compatible enough with their options,
it should still work?

It's not good to hear the server did not restart, but that might be
inherant to the nsd3 PID issues we had.

Paul

3

The comment I made to you in a separate private message, that NSD did
not restart, is because our custom NSD package doesn't use the old SysV
init script on CentOS 6. We instead use an upstart init script to manage
NSD. That's why our NSD instances didn't restart (which is fortunate,
otherwise we would have had outages).

Regards,
Anand

4

Thank you - after updating one of my slaves with no issues and running it for several weeks with no issues I updated the rest including the master with no issues.

It's not common for me that major version upgrades of software "just works" but it seems this time, it did. At least for me.

Hats off to the developers and packagers that made that happen.

5

Thanks for the feedback! It is good to know the migration worked. I had tested it on my own production server but good to hear it works elsewhere too.

There might be an unsolved issue with selinux causing failures - we are investigating a bug report on that.

Paul

6

Paul,

Thank you for your efforts to package NSD 4.1.7 and move it into the
EPEL repository.

It is important that NSD users will move from NSD 3 to NSD 4, as the
support for NSD 3 will end in May 2016. See also announcement
https://open.nlnetlabs.nl/pipermail/nsd-users/2015-May/002100.html

Best regards,

-- Benno