similar to: Fwd: Re: nsd can't bind udp socket: Address already in use

Greetings, Unbound 1.4.20 OS X 10.8.4 - Server NSD 3.2.15 I have installed 'unbound' and it works nicely on my client (test purpose) - Client is MacBook Air. I have installed NSD (will be in replacement of BIND) on said client. All is good but when i try to start NSD Error --> nsd can't bind udp socket: address already in use. Everything is configured to bind to 127.0.0.1. #

Dear all, NSD 4.11.0 is available: https://nlnetlabs.nl/downloads/nsd/nsd-4.11.0.tar.gz sha256 93956d90d45ffa9f84f8ca2f718a42105e4236d094ce032211849f1a12cdc158 pgp https://nlnetlabs.nl/downloads/nsd/nsd-4.11.0.tar.gz.asc Version 4.11.0 sees various small features and bugfixes. One notable feature is that configuration can be reloaded and evaluated on SIGHUP, when enabled with the new

Dear all, NSD 4.11.0rc1 pre-release is available: https://nlnetlabs.nl/downloads/nsd/nsd-4.11.0rc1.tar.gz sha256 7594d014199585c24f6593649bfc657078d411a3f09eb31192a35a7c031c028f pgp https://nlnetlabs.nl/downloads/nsd/nsd-4.11.0rc1.tar.gz.asc Version 4.11.0rc1 sees various small features and bugfixes. One notable feature is that configuration can be reloaded and evaluated on SIGHUP, when

Dear all, We have an emergency quick-fix release, version 4.11.1 for NSD. NSD 4.11.1 is available: https://nlnetlabs.nl/downloads/nsd/nsd-4.11.1.tar.gz sha256 696e50052008de4fa7ab1d818d5b77eb63247eea2f0575114c9592ff9188a614 pgp https://nlnetlabs.nl/downloads/nsd/nsd-4.11.1.tar.gz.asc NSD version 4.11.0 had a serious bug in which applying updates to zones (and other modifications that require a

Hi Andreas, On 16/04/2025 23:17, A. Schulze via nsd-users wrote: > 4. any chance, that https://github.com/NLnetLabs/nsd/pull/437 find it's > way in 4.12? > ?? a similar change in active in unbound-1.23.0rc2 and works well there. This change was heading to 4.12 but we pulled it because it was breaking software that implicitly sends the SOA probe over UDP. Maybe a more lenient

----- Mensagem Original -----=20 Eu boicotaria estas empresas s=F3 pelo fato de financiarem os enjoativos e = rancentos Cassetas, mas me surpreendi ao descobrir que tantos produtos que = eu costumo comprar s=E3o transg=EAnicos. Fui conferir no site do greenpeace= e =E9 verdade!!!!!!!!!!!!! Boicote neles! ----- Original Message -----=20 C A M P A N H A=20 N A T A L S E M B A I X A R I A

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear all, Hereby I announce the bug-fix release of NSD 2.3.7 on our 2.3.x maintenance branch. NSD 2.3.7 is available from: http://www.nlnetlabs.nl/downloads/nsd/nsd-2.3.7.tar.gz SHA1 (nsd-2.3.7.tar.gz) = 4eee0dfdbe823c83e16a4830e97256e66e1d331a This release has the following changes: * Bug #149: Fixed text for NOTAUTH error code. * Fixed

Hello, The NSD documentation on Catalog zones[1] states: > NSD can be a producer of catalog zones as well as a catalog zone consumer, but it is limited to process only a single consumer zone. This can be a shortcoming in some architectures, like when NSD is used as a distribution server, dynamically "collecting" domains from several primary servers (each with its own catalog zone)

Hello, It seems our NSD secondary has triggered some sort of intermittent bug After several weeks/months of running nsd stops forking with the new zone data. A manual nsd-control transfer or even nsd-control force_transfer won?t work, only restart of nsd solves the problem. The only ?hint? I?ve found is that the nsd xfrd messages stops appearing in the logs (while the notify messages keeps

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

B.t.w. I've created a PR for it that resolves it (see https://github.com/NLnetLabs/nsd/pull/346 ), but we may need to discuss if and how to resolve it first. First I'd like to know if your configuration is similar in that the CNAME or DNAME target does contain an allow-query list. Op 03-07-2024 om 10:52 schreef Willem Toorop via nsd-users: > Hi Jamie, > > I can reproduce,

Hi Andreas, The suggestions I captured in GitHub issues. Thanks for sharing. 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. I've added a GitHub issue for this too. Thanks for the suggestions. They make for nice

O que ? CentOS? CentOS Enterprise Linux ? uma distribui??o baseada no Red Hat Enterprise Linux. CentOS Cada vers?o ? suportada por 7 anos (por meio de atualiza??es de seguran?a). CentOS Uma nova vers?o ? liberada a cada 2 anos, e cada vers?o CentOS ? actualizado regularmente (a cada 6 meses) para suportar os hardware mais novos. Isso resulta em uma rede segura, de baixa manuten??o, confi?vel e

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

hi, On 2024-12-27 22:32, Fredrik Pettai via nsd-users wrote: > Hello, > > It seems our NSD secondary has triggered some sort of intermittent bug > After several weeks/months of running nsd stops forking with the new > zone data. > > A manual nsd-control transfer or even nsd-control force_transfer won?t > work, only restart of nsd solves the problem. > The only

On 2025-04-16 14:22 +02, Jannik Peters via nsd-users <nsd-users at lists.nlnetlabs.nl> wrote: > Dear all, > > NSD 4.12.0rc1 pre-release is available: > https://nlnetlabs.nl/downloads/nsd/nsd-4.12.0rc1.tar.gz > sha256 b9085a3fd08b8318ac30715faf1c7698099781eb3520253774a46f74386342e9 > pgp https://nlnetlabs.nl/downloads/nsd/nsd-4.12.0rc1.tar.gz.asc > > > This release

Hi, NSD 4.10.1rc2 pre-release is available: https://nlnetlabs.nl/downloads/nsd/nsd-4.10.1rc2.tar.gz sha256 ce2e82bc673aeff3a71aeb422fa38fb8db0a591edb76c13b0e4dde83ec8253e9 pgp https://nlnetlabs.nl/downloads/nsd/nsd-4.10.1rc2.tar.gz.asc Version 4.10.1 consists primarily of bug fixes. @bilias implemented mutual TLS authentication for zone transfers. Please consult the nsd.conf manual for details

Hi bob., As fas as i know opendns does not support dnssec. which is default enabled in bind9 try switchin your dns forwarders to googles ( which support dnssec ) and see what happens. or.. disable dnssec in bind9 Louis >-----Oorspronkelijk bericht----- >Van: bob at donelsontrophy.net >[mailto:samba-bounces at lists.samba.org] Namens Bob of Donelson Trophy >Verzonden:

Not knowing bind that well, these changes take place in the /etc/bind/named.conf.options file? Is there anywhere else they need changing? --- ------------------------- Bob Wooden of Donelson Trophy 615.885.2846 (main) www.donelsontrophy.com [1] "Everyone deserves an award!!" On 2015-02-06 10:11, L.P.H. van Belle wrote: > Hi bob., > > As fas as i know opendns does not