similar to: NSD compressing RP content

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:

Hi, how can DNS reliability, as experienced by clients on the LAN who are sending queries, be increased? Would I have to set up some sort of cluster consisting of several servers all providing DNS services which is reachable under a single IP address known to the clients? Just setting up several name servers and making them known to the clients for the clients to automatically switch isn't

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

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

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

Hello! Does nsd support ALIAS records or is there a plan to support it somewhen in the future? I didn't find anything about this topic in conjunction with nsd. Afaik there is no RFC for it and I guess therefore nsd does not support it. PowerDNS does for example: https://doc.powerdns.com/authoritative/guides/alias.html Br, Christof -------------- next part -------------- An HTML attachment

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

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

>Regarding whether notifies are still plain UDP. Yes, the config parser >doesn't accept additional arguments to "notify" and judging by the xfrd >code anything to do with notify is using UDP, so no TLS yet. Is there currently or will there by provision for NOTIFY over TCP? Knot-DNS only supports NOTIFY over TCP and not UDP, so interoperabilty is in danger. nsd.conf(5)

On 30/07/2024 22:16, Jan-Piet Mens via nsd-users wrote: Hi Jan-Piet, > Knot-DNS only supports NOTIFY over TCP and not UDP, so interoperabilty > is in > danger. nsd.conf(5) doesn't mention protocol in either notify: or allow- > notify: > so I'm hoping [1] will add this capability. Knot DNS sends NOTIFY only over TCP. However, it will *accept* NOTIFY over both UDP and

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

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

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

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

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

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!

Can nsd 2.3.3 make load balancing? Example: www 600 IN A 10.0.0.1 600 IN A 10.0.0.2 600 IN A 10.0.0.3 Greet Sebastian Schikora

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