search for: bortzmey

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

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".)

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?

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

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

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?

Two name servers of .FR are now NSD machines, a.nic.fr (anycasted) and c.nic.fr.