similar to: Rate-limiting in nsd?

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

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

Package: xen-utils-3.0 Version: 3.0.2+hg9656-1 Severity: grave Justification: renders package unusable When xend starts: [2006-05-22 22:07:18 xend] INFO (SrvDaemon:278) Xend Daemon started [2006-05-22 22:07:18 xend] INFO (SrvDaemon:282) Xend changeset: Thu Apr 27 09:58 :50 2006 +0100 . [2006-05-22 22:07:18 xend] ERROR (SrvDaemon:292) Exception starting xend ((111,

> Could you please try with a Debian kernel image There is one? I do not find it in either etch or sid (or on Alioth). Do I have to recompile a kernel?

-----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

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?

Hi all: I'm currently using NSD 1.2.4 on a FreeBSD host to serve a big domain. I've been looking for new versions of NSD (particularly NSD 2.0.2) on FreeBSD Ports but I haven't found it. Who should add this new version to Ports? Can I make something to include it? I don't have enough experience with FreeBSD and I feel a little bit lost. Best Regards -- Sebastian E. Castro

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

This release is a bug fix release. Please see the README document for configuration and installation instructions. You can download NSD from http://www.nlnetlabs.nl/nsd/ NSD 2.0.2 release notes: BUG FIXES: - Allow the use of a mnemonic for the algorithm field of a DNSKEY record. - Behavior of the zonec -v flag has been modified. By default zonec will

Dear all, Could I use the tool "nsupdate" from the "dnsutils" package to update my zone/record in NSD ? http://docs.freebsd.org/doc/8.0-RELEASE/usr/share/doc/bind9/arm/man.nsupdate.html Thanks by advance.

Hello, I've packaged NSD for Solaris and it's available on OpenCSW. --> http://www.opencsw.org/packages/CSWnsd The package can be easily installed with "pkg-get install nsd". It works out of the box and it contains an SMF manifest for Solaris 10. Feedback is always welcome. Ihsan -- ihsan at dogan.ch http://blog.dogan.ch/

Hello. I wrote utility for batch processing over NSD remote server control. Today only "reload" is supported. Source code are available on github. https://github.com/marmolak/nsd-batch/blob/master/nsd-batch.pl Best regards Robin Hack

hi, I noticed the build-nsdzones.pl only converts the first zone of my named.conf to nsd.zones. It also did not include either a master or notify keyword, even though my bind configuration for that zone had an also-notify keyword. Even not listing an also-notify line did not cause build-nsdzones.pl to process more then one zone. Second, I had a question about the nsd.zones format. Does the

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

The primary (a BIND9) of a zone ("test.") served (as a secondary) by our nsd complains: Jul 16 17:52:45.796 notify: debug 3: zone test/IN: notify response from 192.134.7.251#53: NOTIMP After all, nsd implements the NOTIFY, it logs them and SEC parses the log file to run "nsdc update". Isn't it an error to send a NOTIMP? nsd 1.2.1

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, I just installed nsd 1.2.2, and found that it choked on the following zone file when parsing it as an IPv6 zone file, complaining about out-of-zone data on line 2: @ IN SOA ns.oryx.com. hostmaster.oryx.com. ( 2003091600 10800 3600 2592000 86400 ) 1 IN PTR localhost. Using it only under IPv4 worked. What I'm now using is

An HTML attachment was scrubbed... URL: <http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20230222/50ca00eb/attachment.htm>

BIND has a handy feature $GENERATE directive in zone files that allows you to handle large ranges of things like PTR/A records without having to actually create long lists in very large zonefiles. This was handy for things like IPv4/v6 PTR's and matching A/AAAA records for large dynamic hosts, etc. Does NSD support any type of range generation such at this? -- inoc.net!rblayzor XMPP: