similar to: Static linking against glibc

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

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

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 Anand, Doing it with "nsd -v" is not implemented right now because it's meant to be transparent to users of the library, but I think you're right and it'd be good to show the info. The kernel is selected when the parse function is called. For NSD it makes sense to select one on startup and always use that one. There's a GH issue for that:

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

Hi Anand, Stuart, That is indeed correct. At runtime the CPUID instruction is used to detect which extensions are offered and it chooses based on that. When compiling on x86_64 with SSE4.2 and AVX2 enabled, the binary will actually contain 3 parsers, the most optimal one is used at runtime. Optimized versions can be disabled with --disable-westmere (SSE4.2) and --disable-haswell (AVX2) if

Hello NSD users, I've updated the NSD port in the MacPorts tree to version 3.2.1, so that MacPorts users on OS X can install it with a simple "port install nsd" command. The port has two variants, viz. "stats" and "rootserver". Note that after installing the port, one still needs to copy PORTBASE/etc/nsd/nsd.conf.sample to PORTBASE/etc/nsd/nsd.conf and customise

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:

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 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

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 Haswell architecture, and then run this build on another x86_64 CPU that doesn't have

Hi Robert, NSD doesn't understand the GENERATE directive. You'll have to create your zone files using a script or template engine. Regards, Anand On 20/03/2023 16:29, Robert Blayzor via nsd-users wrote: > BIND has a handy feature $GENERATE directive in zone files that allows > you to handle large ranges of things like PTR/A records without having > to actually create long

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

On Sun, Apr 19, 2020 at 9:26 AM Anand Buddhdev <anandb at ripe.net> wrote: > > On 19/04/2020 14:58, Jeffrey Walton wrote: > > Hi Jeffrey, > > > The offending host is 59.64.129.175. To err on the side of caution we > > attempted to block the entire netblock. According to whois data, > > that's 59.64.128.0-59.64.159.255. > > > > iptables -A

On 17/07/2024 16:57, Jeroen Koekkoek wrote: Hi Jeroen, > That is indeed correct. At runtime the CPUID instruction is used to > detect which extensions are offered and it chooses based on that. When > compiling on x86_64 with SSE4.2 and AVX2 enabled, the binary will > actually contain 3 parsers, the most optimal one is used at runtime. Thanks for this clarification. NSD doesn't

Thanks for the update Jeroen, and for creating the issues to track the suggestions. You didn't answer the parts of my email relating to what happens at compile time, and how the resulting NSD binary is affected depending on what architecture it's compiled on. If you could expand on those, I'd appreciate it. Regards, Anand -------------- next part -------------- An HTML attachment was

Use the 'downgrade' option. https://access.redhat.com/solutions/29617 On Thu, Jun 1, 2017 at 1:46 PM, Anand Buddhdev <anandb at ripe.net> wrote: > We're using ansible to configure our CentOS 6 servers, and we have a > task to install a specific version of a package: > > - name: install thrift2 > yum: name=ripencc-thrift2-{{ version }} > > In this ansible

Hi, virt-install --help Use '--option=?' or '--option help' to see available suboptions See man page for examples and full option syntax. # virt-install --option help usage: virt-install --name NAME --memory MB STORAGE INSTALL [options] virt-install: error: unrecognized arguments: --option help # # virt-install --option=? usage: virt-install --name NAME --memory MB STORAGE

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,

Thought it might also be helpful to confirm that firewalld is not interfering in any way. what is the output of ~$# systemctl status firewalld On Sun, Apr 19, 2020 at 9:30 AM Jeffrey Walton <noloader at gmail.com> wrote: > > On Sun, Apr 19, 2020 at 9:26 AM Anand Buddhdev <anandb at ripe.net> wrote: > > > > On 19/04/2020 14:58, Jeffrey Walton wrote: > > >