search for: ixfrs

...: 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 the appropriate difference records. Neither the zone, nor the IXFRs are ever written to disk. This means that NSD is using RAM for the IXFRs. Could you confirm that NSD with the "store-ixfr" option set to "yes" will use more RAM? Regards, Anand

...n the two zonefiles by keeping one version of the zone in memory, and another version in a temporary file. The temporary file is located in the zonefile directory. This is also where the result is written in a file with the zonefile name, ending with .Sq .ixfr . This is also where NSD reads it when IXFRs are configured for the zone. If other ixfr files exist for the zone, they are renamed to become older IXFR contents for the zone. If the output file already exists with the correct contents, as determined by checking its header, no new file is created. .It Fl n Ar number The number of IXFR versions...

hi, while all files is owned by nsd user and nsd run as nsd the nsd.db is still owned by root user (because the compiler run as root and create this file as root, ok i know just it'd be better if this file is owned by nsd too). another strange thing is that on the slave nsd i've got such messages: ----------------------------------------- zonec: reading zone "lfarkas.org".

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

...r. NSD used a Flex+Bison based zone parser since version 1.4.0. The parser served NSD well, but zones have increased in size and zone loading performance has been problematic for some users. With the integration of simdzone (https://github.com/NLnetLabs/simdzone), performance of loading zones and IXFRs is drastically improved. Quick measurements show improvements ranging anywhere from 3.8x to 1.6x, depending on zone size and database type, though the improvements will be less noticable for NSEC3 zones due to pre-hashing. simdzone leverages SIMD instructions in modern CPUs to improve throughput....

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

...ing in unit test of udb. - Merge #287: Update nsd.conf.5.in. - Fix autoconf 2.69 warnings in configure. - Merge #295: Update e-mail addresses, add ref to support contracts - Fix for interprocess communication to set quit sync command from main process explicitly. - Fix processing of consolidated IXFRs. - Remove on-disk database. - Answer first query for connections accepted just before reload. - Fix: Always instate write handler after reading a query over TCP. - Fix #14: Set timeout to 3s when servicing remaining TCP connections. - Merge #302: Test package fixes. Correct Auxfiles, kill_from_pidf...

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!

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

...or gcc 2.95). - Bugfix #483: Better error message in case of TSIG error. - Bugfix #485: TTL should not be greater than 2^31 - 1. - Fix RCODE when CNAME loop final answer does not exist, should return NXDOMAIN as stated by RFC 6604. - Fix --disable-full-prehash bug, where after multiple incoming IXFRs, NSEC3 can be removed unjustified. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 553 bytes Desc: OpenPGP digital signature URL: <http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20130204/398d2770...

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 >

Hi I'm currently testing the replacement of a samba 3 with LDAP backend with a samba 4 ad-dc. For this, I have a fresh install of: - FreeBSD 10.2 - samba 4.3.3 - bind with dlopen-support: IND 9.10.3-P3 <id:bdaecad> built by make with '--localstatedir=/var' '--disable-linux-caps' '--with-dlopen=yes' '--disable-symtable'

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

I have used tinydns for many many years now and it has always worked very well. I like its simplicity: 1 text file is converted into a cdb database, there's no master/slave environment (all nameservers are equal) and synchronisation is done by rsync. Tinydns is run by runit, a supervise system. I'm looking at NSD now and I think I can use NSD the same way I use tinydns. The only

An HTML attachment was scrubbed... URL: <http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20230222/50ca00eb/attachment.htm>

Andrew & Kenny - Thank You! DSN will talk to me again! I still don't have the dynamic DNS completely right, but God it sure is nice to have nslookup speaking to me again. I couldn't have done it without your help. Ok, here is the status. Like a numer of us, I have the uncanny nack of making life far too difficult for myself. You are goinng to sh!$ when you find out what my