similar to: ANNOUNCEMENT: NSD 2.0.2 released

NSD 2.3.2 is a bugfix release. Please see the README document for configuration and installation instructions. You can download NSD from http://www.nlnetlabs.nl/nsd/ Note: we switched to SHA-1 for tarball digest. 2.3.2 ============= FEATURES: - Bug #101: add support for the SPF record. BUG FIXES: - Bug #100: replaced non-portable use of timegm(3) with portable

This release is an alpha release. We are currently not planning to have a 1.4.0 stable release as we want to prioritize implementing DNSSEC first. The next stable release will then be NSD 2.0.0 with DNSSEC support. This release has some major changes: the database format is much more compact, responses are generated on-the-fly instead of being precompiled in the database, and the new

This release fixes various bugs in the zone compiler. Please see the README document for configuration and installation instructions. You can download NSD from http://www.nlnetlabs.nl/nsd/ NSD 2.1.1 release notes: BUG FIXES: - Bug #81: Handle unknown types correctly. - Bug #82: Zonec: don't report "0 errors" unless -v is specified. - Bug

Hi, NSD 4.10.1rc2 pre-release is available: https://nlnetlabs.nl/downloads/nsd/nsd-4.10.1rc2.tar.gz sha256 ce2e82bc673aeff3a71aeb422fa38fb8db0a591edb76c13b0e4dde83ec8253e9 pgp https://nlnetlabs.nl/downloads/nsd/nsd-4.10.1rc2.tar.gz.asc Version 4.10.1 consists primarily of bug fixes. @bilias implemented mutual TLS authentication for zone transfers. Please consult the nsd.conf manual for details

We upgraded to NSD 3.2.9 (from 3.2.8) because we encountered the problem "Fix denial of existence response for empty non-terminal that looks like a NSEC3-only domain (but has data below it)." (a nasty problem with DNSSEC). But we now have IXFR issues. On one name server, NSD 3.2.9 works fine, zones are IXFRed and work. On another name server, with much more zones (and big ones), we

Dear all, NSD 4.11.0 is available: https://nlnetlabs.nl/downloads/nsd/nsd-4.11.0.tar.gz sha256 93956d90d45ffa9f84f8ca2f718a42105e4236d094ce032211849f1a12cdc158 pgp https://nlnetlabs.nl/downloads/nsd/nsd-4.11.0.tar.gz.asc Version 4.11.0 sees various small features and bugfixes. One notable feature is that configuration can be reloaded and evaluated on SIGHUP, when enabled with the new

Dear all, NSD 4.11.0rc1 pre-release is available: https://nlnetlabs.nl/downloads/nsd/nsd-4.11.0rc1.tar.gz sha256 7594d014199585c24f6593649bfc657078d411a3f09eb31192a35a7c031c028f pgp https://nlnetlabs.nl/downloads/nsd/nsd-4.11.0rc1.tar.gz.asc Version 4.11.0rc1 sees various small features and bugfixes. One notable feature is that configuration can be reloaded and evaluated on SIGHUP, when

Rick, My apologies :) zongo -------- Original Message -------- Subject: Re: [nsd-users] nsd can't bind udp socket: Address already in use Date: Wed, 10 Jul 2013 19:33:20 +0200 From: Rick van Rein (OpenFortress) <rick at openfortress.nl> To: zongo saiba <zongosaiba at gmail.com> zongo, you only sent this to me? -rick On Jul 10, 2013, at 7:04 PM, zongo saiba

Hi Jean Claude, The message is printed when the bind operation failed. Why that happens is hard to say, I'd need more information for that. As the message does not say: address already in use (or similar), I'm guessing the address is not configured? Best regards, Jeroen On Fri, 2023-04-21 at 18:03 +0200, HAKIZIMANA Jean Claude via nsd-users wrote: > Dear nsd Users, > kindly can

Dear NSD users, Here is the release candidate for NSD 3.2.15. This comes with ILNP support, NSD-RRL and different TSIG initialization (it fails if it can't find no suitable algorithms, instead of can't find 'one of the'). Plus some bugfixes. The NSD-RRL implementation is based on the work by Vixie and Schryver. However, because of the code-diversity argument that is at the basis

Hello, The NSD documentation on Catalog zones[1] states: > NSD can be a producer of catalog zones as well as a catalog zone consumer, but it is limited to process only a single consumer zone. This can be a shortcoming in some architectures, like when NSD is used as a distribution server, dynamically "collecting" domains from several primary servers (each with its own catalog zone)

Hi Andreas, The suggestions I captured in GitHub issues. Thanks for sharing. Regarding whether notifies are still plain UDP. Yes, the config parser doesn't accept additional arguments to "notify" and judging by the xfrd code anything to do with notify is using UDP, so no TLS yet. I've added a GitHub issue for this too. Thanks for the suggestions. They make for nice

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear all, Hereby I announce the bug-fix release of NSD 2.3.7 on our 2.3.x maintenance branch. NSD 2.3.7 is available from: http://www.nlnetlabs.nl/downloads/nsd/nsd-2.3.7.tar.gz SHA1 (nsd-2.3.7.tar.gz) = 4eee0dfdbe823c83e16a4830e97256e66e1d331a This release has the following changes: * Bug #149: Fixed text for NOTAUTH error code. * Fixed

B.t.w. I've created a PR for it that resolves it (see https://github.com/NLnetLabs/nsd/pull/346 ), but we may need to discuss if and how to resolve it first. First I'd like to know if your configuration is similar in that the CNAME or DNAME target does contain an allow-query list. Op 03-07-2024 om 10:52 schreef Willem Toorop via nsd-users: > Hi Jamie, > > I can reproduce,

On NetBSD 6.99.28-CURRENT, nsd 3.2.16 works fine, however nsd 4.0.0 is spinning chewing CPU. The logs show: Nov 28 23:07:00 xxx nsd[466]: sendmmsg failed: Resource temporarily unavailable ktruss shows it getting EAGAIN from sendmmsg(2) over and over again. According to the man page: [EAGAIN|EWOULDBLOCK] The socket is marked non-blocking and the requested

Dear nsd Users, kindly can you help me to trace the cause of this error in nsd " nsd[25372]: warning: xfrd: could not bind source address:port to socket: Cannot assign requested address". I use NSD version 4.0.1 Thank you, -------------- next part -------------- An HTML attachment was scrubbed... URL:

NSD 4.10.0rc1 is available: https://nlnetlabs.nl/downloads/nsd/nsd-4.10.0rc1.tar.gz sha256 ad476e82eee5bdabc985e071cabe6a68263dd02eac6278ce2f81798b8c08f19f pgp https://nlnetlabs.nl/downloads/nsd/nsd-4.10.0rc1.tar.gz.asc Version 4.10.0 integrates simdzone and drops the Flex+Bison zone parser. NSD used a Flex+Bison based zone parser since version 1.4.0. The parser served NSD well, but zones have

Good morning, On Tue Apr 28 2009 at 10:34:24 CEST, Jelte Jansen wrote: > We are looking into it (if only because the question comes up about once a > week now) It's been a little more than a week since the question last turned up :) I'd also like to know if any progress has been made to allow NSD to have zones added/removed on the fly, somewhat along the lines of BIND's

Hi, NSD 4.8.0rc1 pre-release is available: https://nlnetlabs.nl/downloads/nsd/nsd-4.8.0rc1.tar.gz sha256 64f1da8f8163340f9d3b352ef8819e3c72c951fdd87cff55dc3b6a6b1ea27942 pgp https://nlnetlabs.nl/downloads/nsd/nsd-4.8.0rc1.tar.gz.asc This release introduces PROXYv2 support and faster statistics gathering, removes the database option and fixes bugs. The proxy protocol support is an implementation

Hi there! I remember reading that you cannot reload new zone files on the fly and require a full restart of the nsd daemon? We are evaluating multiple DNS servers that have better performance comparing to bind, but will require quite heavy zone reload (new and existing) every 10 minutes or so. Downtime (even 1-3 secs) is not the option. Thanks!