similar to: nsd replies with NOTIMP when receiving a NOTIFY?

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

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

I try to change the configuration of a runnung NSD 3 instance. "nsdc reload" apparently does not read the config (only the database). "nsdc restart" seems to do the trick but is there a way to have the configuration change taken into account without stopping the service for the time it takes to restart?

People are proposing rate-limiting built into BIND, to defend against some DoS attackes (a proposal <http://fanf.livejournal.com/122111.html> and its implementation <https://github.com/fanf2/bind-9/blob/master/doc/misc/ratelimiting>). What is the current thinking for NSD? (It is a truly open question, do not take it as "this guy requires rate-limiting in NSD".)

On 30/07/2024 22:16, Jan-Piet Mens via nsd-users wrote: Hi Jan-Piet, > Knot-DNS only supports NOTIFY over TCP and not UDP, so interoperabilty > is in > danger. nsd.conf(5) doesn't mention protocol in either notify: or allow- > notify: > so I'm hoping [1] will add this capability. Knot DNS sends NOTIFY only over TCP. However, it will *accept* NOTIFY over both UDP and

>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. Is there currently or will there by provision for NOTIFY over TCP? Knot-DNS only supports NOTIFY over TCP and not UDP, so interoperabilty is in danger. nsd.conf(5)

Hi, I've been working on a replacement for nsd-xfer/bind-xfer for the use with NSD for some evenings now, and since I believe that at least some of you do have the same problem I experienced during my transition to NSD (that is, bind-xfer is only available in BIND8, which is sometimes a little bit peeky in being compiled, plus the many invokations of that program during the regular

Hi, I have a query regarding running a manual update of nsd via: # nsdc update My NSD server is accepting notifications from two servers. From my nsd.conf: # master 1 allow-notify: X.X.X.X NOKEY request-xfr: AXFR X.X.X.X NOKEY # master 2 allow-notify: Y.Y.Y.Y NOKEY request-xfr: AXFR Y.Y.Y.Y NOKEY Are both servers sequentially queried each time

I'm trying to set up a machine which will be running multiple instances of NSD to serve different sets of zones from different interfaces. What I'm running into is that I can't specify different PID files to refer to on the command line. Are there any shortcuts or do I need to go write a patch? Any other implications of multiple instances? --

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

I wonder how to process the statistics logged by nsd. We compile with --enable-bind8-stats and I thought we would be able to reuse the Perl script that translated our BIND8 statistics to MRTG. But the script has problems, probably because nsd has several daemons, not just one, and each one is logging statistics. Aug 4 10:34:01 ns2 nsd[24573]: NSTATS 1059986041 1059979224 A=292259 NS=4886

Hi! I've got troubles with dynamic dns updates. Ubuntu: 12.04 / Samba 4.0.0 / followed off. howto Winsrv: Server 2k8R2 root at tuxsrv:/home/schau# samba -V Version 4.1.0pre1-GIT-94f11e9 root at tuxsrv:/home/schau# kinit administrator at SCHAU.LOCAL Password for administrator at SCHAU.LOCAL: root at tuxsrv:/home/schau# klist Ticket cache: FILE:/tmp/krb5cc_0 Default principal: administrator

Hi, I'm doing some quick tests with nsd-4.0.0b5 and (rc2). And found something strange when changing (nsd-control reconfig) one zone from: zone: name: 10.in-addr.arpa zonefile: /zones/empty.zone to zone: name: 10.in-addr.arpa request-xfr: 192.168.122.12 NOKEY allow-notify: 192.168.122.12 NOKEY zonefile: /zones/slave/10.rev and doing nsd-control reconfig. After

Hello I have this problem since a week or so: The nsd daemon crashes unexpectedly and the nsd log files shows this: [1200299533] nsd[3736]: info: XSTATS 1200299533 1200298484 RR=0 RNXD=0 RFwdR=0 RDupR=0 RFail=0 RFErr=0 RErr=0 RAXFR=0 RLame=0 ROpts=0 SSysQ=0 SAns=40 SFwdQ=0 SDupQ=0 SErr=0 RQ=37 RIQ=0 RFwdQ=0 RDupQ=0 RTCP=0 SFwdR=0 SFail=30 SFErr=0 SNaAns=0 SNXD=0 RUQ=0 RURQ=0 RUXFR=0 RUUpd=1

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

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, while all files is owned by nsd user and nsd run as nsd the nsd.db is still owned by root user (because the compiler run as root and create this file as root, ok i know just it'd be better if this file is owned by nsd too). another strange thing is that on the slave nsd i've got such messages: ----------------------------------------- zonec: reading zone "lfarkas.org".

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

Hello, This topic has been discussed at least a couple of times in the past, but is there currently any way to make NSD ignore out-of-zone data or other errors in the zones or make NSD skip invalid zones? At least with NSD 3.2.16 or earlier any such errors cause NSD rebuild fail and thus prevent NSD from restarting. This is especially problematic in environments where NSD acts as a slave server

Hello NSD users, I've updated the NSD port in the MacPorts tree to version 3.2.1, so that MacPorts users on OS X can install it with a simple "port install nsd" command. The port has two variants, viz. "stats" and "rootserver". Note that after installing the port, one still needs to copy PORTBASE/etc/nsd/nsd.conf.sample to PORTBASE/etc/nsd/nsd.conf and customise