Displaying 20 results from an estimated 900 matches similar to: "About timestamps in logs and zonestatus"
2024 Feb 27
1
About timestamps in logs and zonestatus
Hi Peter,
NSD processes updates in batches. xfrd receives the [AI]XFR and
schedules a reload for the main process, which in turn forks new serve
children. The served-serial is updated after main reports success, the
commit-serial (update written to disk) is updated before the reload (to
explain the serials).
The difference in timestamp can be explained by the fact that NSD looks
up if the serial
2024 Feb 28
1
About timestamps in logs and zonestatus
Hi Jeroen,
I just realised that the version I use is very old -- 4.1. So first what I
should do -- updating it and only then come here , asking for clarification.
??, 27 ????. 2024??. ? 14:19, Jeroen Koekkoek <jeroen at nlnetlabs.nl>:
> Hi Peter,
>
> NSD processes updates in batches. xfrd receives the [AI]XFR and
> schedules a reload for the main process, which in turn forks
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
2002 Mar 04
2
SGI XFS 1.0.2a, ACLs and samba 2.2.3a with win2k perms
Hi,
I haven't been able to find any doco that explicity states whether it is
supported, so I am hoping someone out there can answer the following
questions:
Is it possible for a folder/file in a samba share to have win2k security
permissions assigned to it? For example, I want my samba server to
participate in an existing Win2k domain. I want users to be able to set
their own
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
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 Oct 16
1
SIGSEGV in rbtree_find_less_equal
Hi Chris,
I've properly started looking into this yesterday. NSD definitely
shouldn't crash, still working on that.
However, the provided zone is invalid too(?) I'm not the foremost
expert on NSEC3 (or even DNSSEC), but is seems an NSEC3 is missing for
bar.foo.com. Empty non-terminals should still have an NSEC3 RR.
(Of course, the delegation point should be at bar.foo.com. too and
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
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 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
2024 Oct 09
1
SIGSEGV in rbtree_find_less_equal
Hi Chris,
I can reproduce with your zone. Thanks!
Best,
Jeroen
On Tue, 2024-10-08 at 14:07 +0000, Chris LaVallee wrote:
>
> 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
>
>
>
>
>
>
>
>
>
>
>
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:
2012 Jun 08
2
Best practices to switch from BIND to NSD
Hi,
I'm a sys admin and currently working for a french hosting company. We
provide DNS services to our customers and at the moment we are using BIND
on Debian servers. BIND is a good software but we don't need a recursing
DNS for our public DNS, and we needed better security than what BIND provides.
So I made the suggestion to replace BIND by another DNS software.
NSD appears to be the
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 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
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
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
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!
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
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: