search for: nlnetlabs

...on it?s much more challenging to do due to NSD architecture than it was to implement it in PowerDNS. But if NSD developers some day feel bored, perhaps implementing ALIAS would solve that ? ;-) Rubens > Em 11 de jan. de 2024, ?(s) 07:49, Klaus Darilion via nsd-users <nsd-users at lists.nlnetlabs.nl> escreveu: > > 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...

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 new serve > children. The served-serial is updated after main reports success, the > commit-serial (update written to disk) is up...

...AIN|EWOULDBLOCK] The socket is marked non-blocking and the requested operation would block. Sounds like it's blocking when it shouldn't? -Dustin -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20131128/170fab59/attachment.htm>

...__________________________________________ Fussy? Opinionated? Impossible to please? Perfect. Join Yahoo!'s user panel and lay it on us. http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20070806/bd76d296/attachment.htm>

...f you build something new, don't use ALIAS, it can cause you problems later due to incompatibilities -- Klaus Darilion, Head of Operations nic.at GmbH, Jakob-Haringer-Stra?e 8/V 5020 Salzburg, Austria > -----Urspr?ngliche Nachricht----- > Von: nsd-users <nsd-users-bounces at lists.nlnetlabs.nl> Im Auftrag von > Wolf Christof via nsd-users > Gesendet: Mittwoch, 10. J?nner 2024 15:41 > An: nsd-users at lists.nlnetlabs.nl > Cc: Wasik Robert <robert.wasik at A1.at> > Betreff: [nsd-users] support for ALIAS records > > Hello! > > > > Does nsd su...

...checkconf] Error 1 ``` I have done the following: # Install prerequisites $ sudo aptitude install subversion libssl-dev autoconf make byacc flex bison build-essential -y # Clone NSD Repository $ mkdir $HOME/src $ cd $HOME/src $ svn co http://www.nlnetlabs.nl/svn/nsd/ nsd # Generate `configure` program $ cd $HOME/src/nsd/tags/NSD_4_0_0_imp_5 $ autoreconf --install # Configure $ cd $HOME/src/nsd/tags/NSD_4_0_0_imp_5 $ ./configure --prefix=/usr --sysconfdir=/etc/nsd4 --localstatedir=/var/run/nsd4 --with-configdir=/etc/nsd4...

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

...s error in nsd > "?nsd[25372]: warning: xfrd: could not bind source address:port to > socket: Cannot assign requested address". > I use?NSD version 4.0.1 > > Thank?you, > _______________________________________________ > nsd-users mailing list > nsd-users at lists.nlnetlabs.nl > https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users

...s in 3.8e-05 seconds Feb 26 18:47:34 slave-server nsd[777]: zone testzone.test serial 2024022601 is updated to 2024022603. -- Is there any problem Exterminatus cannot solve? I have not found one yet. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20240227/4dbac526/attachment.htm>

...erver nsd[777]: zone testzone.test serial > 2024022601 is updated to 2024022603. > > > -- > Is there any problem Exterminatus cannot solve? I have not found one > yet. > > _______________________________________________ > nsd-users mailing list > nsd-users at lists.nlnetlabs.nl > https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users

...00? ? ?IN? ? ?SRV? ? ? 0 5 5222 > example.com > > > Thanking you > Sagar Acharya > https://humaaraartha.in > > P.S. Please cc me, I'm not subscribed to this list.? > _______________________________________________ > nsd-users mailing list > nsd-users at lists.nlnetlabs.nl > https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users

...t is at the basis of NSD work but also because of specifics of the NSD architecture, it is an independent implementation. The implementation shares the main ideas that prevent false positives: the fallback to TCP and a fine grained (albeit different) query classification mechanism. See https://www.nlnetlabs.nl/blog/2012/10/11/nsd-ratelimit/ for some of the details. RRL is not enabled by default. Although we are confident about code stability, did extensive testing, and a performed a usual beta-release cycle which gave the code exposure, the methodology is rather new and there is relatively little ope...

...6400 IN CNAME www.google.com.test.com. www.google.com.test.com. 6400 IN CNAME www.google.com.test.com. www.google.com.test.com. 6400 IN CNAME www.google.com.test.com. Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20131119/a19d6094/attachment.htm>

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

On Jan 01 00:05:09, jamie at catflap.org wrote: > Jan Stary via nsd-users <nsd-users at lists.nlnetlabs.nl> wrote: > > > On Dec 31 11:43:56, paul at nohats.ca wrote: > > > Why not go to xml and use xml2man / pandoc ? > > > > Because it is a terrible manpage format > > and the toolchain produces broken crap. > > I have no specific knowledge on this, but w...

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

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

Per RFC 8501 seciont 2.2 https://datatracker.ietf.org/doc/html/rfc8501 I have attempted to use a wildcard on a /64 boundary within a zonefile for NSD, but it doesn't not appear to work. PTR lookups fail... tested with, ie: $ORIGIN 1.1.0.0.8.5.1.b.2.2.5.2.ip6.arpa. * PTR my.fqdn.net. Did not work... or would you have to use? (not tested) *.*.*.*.*.*.*.*.*.*.*.* PTR .... --

...oblems claiming a port are always the same and not something you would resolve with trying again or rebooting. Let's not turn UNIX into Windows, shall we? ;-) >> >> -Rick >> _______________________________________________ >> nsd-users mailing list >> nsd-users at NLnetLabs.nl >> http://open.nlnetlabs.nl/mailman/listinfo/nsd-users > Thank you guys for all your reply. > Unbound and NSD working beautifully. NSD being the authoritative on 127.0.0.1 > NSD is running on port 49152 with queries forwarded to that port from unbound on 127.0.0.1 at 49152. > W...

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