Displaying 20 results from an estimated 2000 matches similar to: "Build all NSD features by default"
2019 Dec 28
2
tinydns to nsd
On Sat, 28 Dec 2019 17:02:09 +0100
richard lucassen via nsd-users <nsd-users at lists.nlnetlabs.nl> wrote:
> The problem is (was) that I used "include:" statements in nsd.conf
> to load zone information. Apparently nsd does not reread the include
> files upon a SIGHUP. I scripted everything into 1 file and a HUP
> rereads the zone info now.
Wrong, I made a mistake it
2013 Feb 04
1
NSD 3.2.15 released (+RRL)
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
2024 Jun 27
1
NSD 4.10.0 compile failure in Homebrew
Hi NSD developers,
I submitted a merge request in Homebrew to update NSD to 4.10.0. The
compile failed, and I don't know what the error means and how to fix it.
Could one of you please take a look?
https://github.com/Homebrew/homebrew-core/pull/175796
Regards,
Anand
2025 Apr 16
4
NSD 4.12.0rc1 pre-release
Dear all,
NSD 4.12.0rc1 pre-release is available:
https://nlnetlabs.nl/downloads/nsd/nsd-4.12.0rc1.tar.gz
sha256 b9085a3fd08b8318ac30715faf1c7698099781eb3520253774a46f74386342e9
pgp https://nlnetlabs.nl/downloads/nsd/nsd-4.12.0rc1.tar.gz.asc
This release introduces Prometheus metrics that can be compiled with
`--enable-prometheus-metrics` and configured with `enable-metrics` (see
2025 Apr 16
1
NSD 4.12.0rc1 pre-release
Hi Jannik,
What's the rationale behind the "--enable-prometheus-metrics" compile-time
option? If this code were compiled by default, would it do any harm?
The reason I'm asking this is that features that can be enabled/disabled at
compile-time make package distribution complicated. It can result in a
scenario where NSD packages on different operating systems or distributions
2008 Jan 15
1
problem using nsd
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
2024 Apr 25
3
NSD 4.10.0rc1 pre-release
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
2013 Nov 06
1
Frequent RRL false negatives when using multiple server processes on Linux
Hi,
Please advise how to use Response Rate Limiting on a server which has
multiple NSD server processes (nsd.conf server section has server-count
> 1).
We have a problem with NSD v3.2.16 repeatedly unblocking and blocking
again a single source which is flooding positive queries at a ~steady
700 qps rate. rrl-ratelimit setting is the default 200 qps. The
unblock-block happens multiple times
2024 Jul 17
1
Run-time effects of new SIMD code
On 2024/07/17 15:47, Anand Buddhdev via nsd-users wrote:
> Hi NSD developers,
>
> I've been following recent discussion and activity around building NSD 4.10, triggered?by build
> failure in Homebrew. I see that you added some code to detect more things and adjust the build
> based on what type of processor is detected.
>
> If one were to build NSD on an x86_64 CPU with
2023 Mar 20
2
NSD zone file GENERATE directive
On 3/20/23 13:41, Anand Buddhdev via nsd-users wrote:
> Hi Robert,
>
> NSD doesn't understand the GENERATE directive. You'll have to create
> your zone files using a script or template engine.
Understood but certainly not helpful with large dynamic IPv6 PTR's...
Not that dynamic hosts NEED PTR's, but would still be nice to have.
--
inoc.net!rblayzor
XMPP:
2013 Sep 26
1
Is nsupdate works for NSD ?
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.
2024 May 17
1
query: bad tsig signature for key
hi,
At least with a recent version if it is a time sync issue nsd will do a specific log msg that.
Laura,
can you send over the actual configuration?
(maybe replacing the key with a placeholder or rotating the keys afterwards)
It sounds strange if nsd checks tsig on the notify, but allow xfr without it.
Regards,
Tam?s
May 16, 2024 16:14:59 Anand Buddhdev via nsd-users <nsd-users at
2023 Dec 05
1
Question on slave
On 04/12/2023 13:47, Jean-Christophe Boggio via nsd-users wrote:
Hi Jean-Christophe,
> When syncing between master and slaves, am I supposed to see new files
> appear in the slave's "zonesdir" directory? Because, as you might
> expect, I see nothing here. Is this behavior normal? From what I
> understand, the slave "caches" the data in /var/lib/nsd/nsd.db
2011 Dec 30
1
Question about "server-count" config option
Hi there,
I have a question about the "server-count" option. nsd.conf(5) simply
states that it tells NSD to "start this many NSD servers", with no
further commentary.
Is there a situation where this value would ever be anything other than
1? Should it equal the number of available CPU cores?
Cheers,
--
Gavin Brown
Chief Technology Officer
CentralNic Ltd
Innovative,
2013 Jul 10
4
nsd can't bind udp socket: Address already in use
Greetings,
Unbound 1.4.20
OS X 10.8.4 - Server
NSD 3.2.15
I have installed 'unbound' and it works nicely on my client (test
purpose) - Client is MacBook Air.
I have installed NSD (will be in replacement of BIND) on said client.
All is good but when i try to start NSD
Error --> nsd can't bind udp socket: address already in use.
Everything is configured to bind to 127.0.0.1.
#
2024 Dec 28
2
NSD stops forking with newer zone data
hi,
On 2024-12-27 22:32, Fredrik Pettai via nsd-users wrote:
> Hello,
>
> It seems our NSD secondary has triggered some sort of intermittent bug
> After several weeks/months of running nsd stops forking with the new
> zone data.
>
> A manual nsd-control transfer or even nsd-control force_transfer won?t
> work, only restart of nsd solves the problem.
> The only
2023 Jul 27
1
High memory consumption for small AXFR
Hello!
I use NSD 4.7.0 self compiled:
Configure line: --build=x86_64-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-option-checking --disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu --runstatedir=/run --disable-maintainer-mode --disable-dependency-tracking
2023 Apr 24
1
nsd issue
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
2013 Nov 29
2
nsd 4.0 EAGAIN loop in sendmmsg(2)
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
2023 Dec 11
1
Question about "store-ixfr"
Hi NSD developers,
I have been experimenting with the "store-ixfr" feature in NSD. I have a
configuration with:
server:
zonefiles-write: 0
pattern:
store-ixfr: yes
With this configuration, NSD transfers zones from a primary, and keeps
them in RAM. When the zones are updated, it receives and stores the IXFR
in RAM too. I can query NSD with the IXFR qtype, and it replies with