NSD 4.1.27rc1 pre-release

NSD
1

Hi,

NSD 4.1.27rc1 pre-release is available:
https://www.nlnetlabs.nl/downloads/nsd/nsd-4.1.27rc1.tar.gz
sha256 186b746d9230a129e3b3d5fc1e26cc25f176b9ae6c8974b14d856cff212d7e1e
pgp https://www.nlnetlabs.nl/downloads/nsd/nsd-4.1.27rc1.tar.gz

This is the maintainers pre-release of the NSD 4.1.27rc1 release.

This release contains improved deny-any responses, and on-the-fly
changes for tsig keys via nsd-control. There is a number of bug fixes
as well.

4.1.27

2

compiled and installed on some lab systems ...

Andreas

3

Hi,

NSD 4.1.27 is available:
https://www.nlnetlabs.nl/downloads/nsd/nsd-4.1.27.tar.gz
sha256 1bab5f30406cabac2f2cc95f8af6dfe20581646a75a70c091845e04d325f4eea
pgp https://www.nlnetlabs.nl/downloads/nsd/nsd-4.1.27.tar.gz.asc

This release contains improved deny-any responses, and on-the-fly
changes for tsig keys via nsd-control. There is a number of bug fixes
as well.

4.1.27

4

thanks for the release!

After update my nsd failed to start with this message:
[2019-03-25 17:00:22.089] nsd[16241]: notice: nsd starting (NSD 4.1.27)
[2019-03-25 17:00:22.089] nsd[16241]: error: can't bind udp socket: Address already in use
[2019-03-25 17:00:22.089] nsd[16241]: error: server initialization failed, nsd could not be started

would it be possible to be more verbose abound which IP and which Port?
I think I could fix my fault but with a more precise error it would be easier.

Andreas

5

I configured NSD to serve 853 (with the TLS-patch we polished @IETF Hackathon) but the port was used by unbound, too :-/
So probably the TLS-patch needs to be verbose...

Andreas

6

Hi Andreas,

NSD 4.1.27 is available:
https://www.nlnetlabs.nl/downloads/nsd/nsd-4.1.27.tar.gz

thanks for the release!

After update my nsd failed to start with this message:
[2019-03-25 17:00:22.089] nsd[16241]: notice: nsd starting (NSD 4.1.27)
[2019-03-25 17:00:22.089] nsd[16241]: error: can't bind udp socket: Address already in use
[2019-03-25 17:00:22.089] nsd[16241]: error: server initialization failed, nsd could not be started

would it be possible to be more verbose abound which IP and which Port?
I think I could fix my fault but with a more precise error it would be easier.

Certainly, fixed it to print that for bind socket failures. Thanks for
the report and test of TLS patch.

Best regards, Wouter