similar to: NUDGE: Levels of verbosity?

Greetings. I am starting to use NSD, and would like to get some indication of when my server is being queried. The doc for "verbosity: <level>" aren't too specific. What do the various values mean? (This question can also be interpreted as a bug report for the nsd.conf man page...) --Paul Hoffman

On 9 Aug 2015, at 8:46, Benny Pedersen wrote: > Paul Hoffman skrev den 2015-08-09 17:40: > >> Initializing mail storage from mail_location parameter failed: mbox: >> mbox root directory can't be a file >> >> Which bit am I missing here? > > sudo doveadm import -u Foo mbox:/home/phoffman/project1/ "Project 1" > all > > untested When I

On 3 Aug 2015, at 7:16, Steffen Kaiser wrote: > On Mon, 3 Aug 2015, Paul Hoffman wrote: >> On 2 Aug 2015, at 23:27, Steffen Kaiser wrote: >>> On Sun, 2 Aug 2015, Paul Hoffman wrote: >>> >>>> Greetings. I have a bunch of mbox files that I want to import to an >>>> existing user, each into a new mailbox. That is, I want to import >>>>

On 08/09/15 13:36, Benny Pedersen wrote: > Paul Hoffman skrev den 2015-08-09 20:20: > >> Fatal: Import namespace initialization failed: Initializing mail >> storage from mail_location parameter failed: >> mkdir(/home/phoffman/project1) failed: Permission denied >> (euid=1013(phoffprop) egid=1013(phoffprop) missing +w perm: >> /home/phoffman, dir owned by

Paul Hoffman skrev den 2015-08-09 20:20: > Fatal: Import namespace initialization failed: Initializing mail > storage from mail_location parameter failed: > mkdir(/home/phoffman/project1) failed: Permission denied > (euid=1013(phoffprop) egid=1013(phoffprop) missing +w perm: > /home/phoffman, dir owned by 1001:1001 mode=0755) > > Does this error indicate that it is trying

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

https://bugzilla.samba.org/show_bug.cgi?id=6995 Summary: Suggested new verbosity level Product: rsync Version: 2.6.9 Platform: All OS/Version: Other Status: NEW Severity: minor Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: phoffman at proper.com

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

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

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

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

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

Paul Hoffman skrev den 2015-08-09 17:40: > Initializing mail storage from mail_location parameter failed: mbox: > mbox root directory can't be a file > > Which bit am I missing here? sudo doveadm import -u Foo mbox:/home/phoffman/project1/ "Project 1" all untested

Dear All, Please help me understand why timestamps in logs are different from those in nsd-control zonestatus output: served-serial: "2024022603 since 2024-02-27T08:07:51" commit-serial: "2024022603 since 2024-02-27T08:07:51" Feb 26 18:47:34 slave-server nsd[780]: zone testzone.test. received update to serial 2024022603 at 2024-02-26T18:47:33 from

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

Could someone kindly explain what "query: bad tsig signature for key" means and how to fix it ? I have quadruple checked (a) tsig key matches both sides (b) tsig algo matches both sides. Primary is PowerDNS 4.9.0 (from the PowerDNS repo) Secondaries are NSD 4.6.1 (from Debian Bookworm distro repo) The secondaries do not receive notifies from primary, instead posting the above error

Hi Jean-Christophe, Anand's answer is entirely correct. Once 4.8.0 is released, zone files will be written once per hour by default. Best regards, Jeroen On Tue, 2023-12-05 at 10:48 +0100, Anand Buddhdev via nsd-users wrote: > On 04/12/2023 13:47, Jean-Christophe Boggio via nsd-users wrote: > > Hi Jean-Christophe, > > > When syncing between master and slaves, am I

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

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

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