Displaying 20 results from an estimated 1000 matches similar to: "NSD 4.8.0rc1 pre-release"
2012 Jul 23
1
[PATCH] nsd-patch: fix segfault after renaming slave zone
Hi all,
we have discovered a segfault in nsd-patch when renaming slave zone in nsd
config file if some data for this zone still exists in the IXFR diff
database.
In my case, the zone "black" was renamed to "blackinwhite":
> root at ggd115:/cage/nsd/var/nsd/zones#nsd-patch -c
> /cage/nsd/etc/nsd-dns-slave.conf
> reading database
> reading updates to database
>
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 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
2012 Mar 05
3
IXFR regression in nsd 3.2.9?
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
2023 Jun 26
1
NSD reload and restart : in-memory data
Hi,
I'm new to NSD and would really appreciate if someone can point me to the
right direction.
I have like 8 NSD servers (secondary) serving around 30,000 zones.
Zone updates are transferred from the primary DNS servers by AXFR/IXFR.
The 8 NSD servers do not save the zones file on disk but are only held in
memory.
Therefore after NSD service is restarted zone transfer requests are being
2007 Aug 06
2
NSD reload
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!
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
2022 Dec 31
1
rewrite manpages to mdoc(7)
Dear authors of NSD,
currently, the manpages that come with NSD
are written in the traditional man(7) markup language.
I am proposing to rewrite them into the semantic markup
of the mdoc(7) language. I am willing to do the work.
See a version of nsd-checkzone.8 below as an example.
Both the man(7) and mdoc(7) languages have been around for decades,
and are supported by the prevalent formatters:
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
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
2005 Dec 05
1
ANNOUNCEMENT: NSD 2.3.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
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 Feb 22
1
NSDadmin - NSD web management interface
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20230222/50ca00eb/attachment.htm>
2023 Apr 21
1
nsd issue
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:
2024 Oct 23
1
Multiple consumer catalog zones support in NSD
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)
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 Jul 24
2
NSD 4.10.1rc2 pre-release
Am 23.07.24 um 17:28 schrieb Jeroen Koekkoek via nsd-users:
> NSD 4.10.1rc2 pre-release is available:
no compile time warnings while building on debian bookworm/x86_64
> @bilias implemented mutual TLS authentication for zone transfers.
> Please consult the nsd.conf manual for details on the newly introduced
> configuration options tls-auth-port and tls-auth-xfr-only.
this is an nice
2011 Oct 30
1
reloading NSD zone configuration
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
2024 Jul 03
1
NSD incorrectly logging DNAME as refused?
I just noticed this with NSD 4.10.0 (and earlier versions - it's not a
new regression))
I have nsd set to log refused requests to syslog.
After adding a DNAME type into my dns for one sub-zone that is being moved,
I noticed that legitimate requests for hosts under that subdomain are working
as expected, howerver they are being logged as refused.
As a quick replicable test, I just did this
2024 Jul 23
1
NSD 4.10.1rc2 pre-release
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