Displaying 20 results from an estimated 30000 matches similar to: "systemd service files for nsd4?"
2013 Mar 07
1
systemd unit files for NSD launch in chroot?
Hi,
I'm starting to migrate a number of authoritative nameservers on small
VMs from bind9 to NSD.
At the same time, I'm switching all inits from sysvinit to systemd.
Cribbing systemd unit files from Fedora for NSD
(http://pkgs.fedoraproject.org/cgit/nsd.git/tree/), they're
straightforward enough -- but seem to ignore proper chroot
setup/startup.
I've poked in current NSD 3x
2013 Mar 11
1
nsd4 process weirdness?
Hi,
I was playing with the munin plugin in nsd4 beta4, and saw some strange
errors. Directly after starting nsd on linux, I'm seeing:
$ ps ax -o pid,ppid,user,args | grep nsd
1638 1 nsd /usr/sbin/nsd -c /etc/nsd/nsd.conf
1641 1638 nsd /usr/sbin/nsd -c /etc/nsd/nsd.conf
1647 1641 nsd /usr/sbin/nsd -c /etc/nsd/nsd.conf
$ sudo munin-run nsd_munin_memory
2012 Nov 28
1
Build error of NSD4 on Debian Squeeze
Hello World,
I am trying to build NSD4 on Debian Squeeze and I get the following
errors when running `make`.
```
$ pwd
/home/wiz/src/nsd/tags/NSD_4_0_0_imp_5
$ make
[... output omitted ...]
gcc -g -O2 -o nsd-checkconf answer.o axfr.o buffer.o configlexer.o
configparse
acket.o query.o rbtree.o radtree.o rdata.o region-allocator.o tsig.o
tsig-opens
4_pton.o b64_ntop.o -lcrypto
configparser.o: In
2013 Jan 28
1
Featurerequest for nsd4
Hello Wouter,
We used tinydns for many years. After migration to nsd3 we miss only one feature present in tinydns only:
tinydns may switch addresses by decreasing the ttl for old data and serve new data
starting from a fixed timestamp.
http://cr.yp.to/djbdns/tinydns-data.html:
You may include a timestamp on each line. If ttl is nonzero (or omitted),
the timestamp is a starting time for the
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 19
2
* CNAME loop
Hi,
I'm testing:
$ sudo nsd-control status
version: 4.0.1
verbosity: 2
I found a loop problem with this record:
* IN CNAME none
("none" means no matching record in zone and therefore match * again)
Queries that use "* CNAME" will result in a loop. The response will use TCP
and will be limited to 65k bytes
$ dig @127.0.0.1 sdfgsfg.test.com
;; Truncated,
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
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
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
2013 Oct 18
1
nsd-4.0.0b5(and rc2) and changing zone from master to slave ?
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
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 Jan 12
1
error: cannot write zone : Permission denied
Hello,
NSD 4.8.0 running on FreeBSD 13.2-RELEASE-p9 and serving both plain
and DNSSEC signed zones.
I noticed Permission denied errors in the logs for all domains listed
in nsd.conf:
[2024-01-12 12:20:05.710] nsd[8655]: info: writing zone
domain-plain.org to file domain-plain.org
[2024-01-12 12:20:05.710] nsd[8655]: error: cannot write zone
domain-plain.org file domain-plain.org~: Permission
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
2024 Oct 02
2
SIGSEGV in rbtree_find_less_equal
Hi,
I found a reproducible seg fault with a DNSSEC signed zone and overlapping config. I'm running NSD 4.10.1. Here's how to reproduce.
2 zones in nsd.conf:
zone:
name: "foo.com."
zonefile: "/zones/foo.com.zone.signed"
zone:
name: "bar.foo.com."
zonefile: "/zones/bar.foo.com.zone"
Zone files:
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
2024 Oct 08
1
SIGSEGV in rbtree_find_less_equal
Hi Chris,
I'm having trouble trying to reproduce the issue locally.
Like you I configure two zones.
zone:
name: example.com.
zonefile: example.com.zone.signed
zone:
name: bar.example.com.
zonefile: bar.example.com.zone
The file bar.example.com.zone does not exist. After touching and
reloading the signed zone, no segfault occurs. I've tried with and
without the
2024 Oct 08
1
SIGSEGV in rbtree_find_less_equal
Hi Jeroen,
Attached is the zone I used. Did you add the record for a.bar ?
Ex:
a.bar 300 IN NS ns.somewhere.net.
Chris
________________________________
From: Jeroen Koekkoek <jeroen at nlnetlabs.nl>
Sent: Tuesday, October 8, 2024 5:33 AM
To: Chris LaVallee <clavallee at edg.io>; nsd-users at lists.nlnetlabs.nl <nsd-users at lists.nlnetlabs.nl>
Subject: Re:
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
2024 Jan 11
1
support for ALIAS records
While SVCB/HTTPS provides a better solution for the browsing use case, I see other use cases where ALIAS/ANAME would be ideal, notably in apex RRs.
So while fostering SVCB/HTTPS deployment is a good thing, I wouldn?t mind name server software implementing ALIAS. Including NSD, but I reckon it?s much more challenging to do due to NSD architecture than it was to implement it in PowerDNS.
But if
2024 Jan 11
1
support for ALIAS records
Hi Christof!
AFAIK, PowerDNS is the only open source name server that supports ALIAS. There was an idea to standardize ALIAS as "ANAME" (https://datatracker.ietf.org/doc/draft-ietf-dnsop-aname/), but the idea was dropped in favor of SVCB/HTTPS record https://datatracker.ietf.org/doc/rfc9460/. So now we have to wait until all Browser vendors implement SVCB/HTTPS.
Regards
Klaus
PS: If