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

Rick, My apologies :) zongo -------- Original Message -------- Subject: Re: [nsd-users] nsd can't bind udp socket: Address already in use Date: Wed, 10 Jul 2013 19:33:20 +0200 From: Rick van Rein (OpenFortress) <rick at openfortress.nl> To: zongo saiba <zongosaiba at gmail.com> zongo, you only sent this to me? -rick On Jul 10, 2013, at 7:04 PM, zongo saiba

Hello, while investigating a report from Jan-Piet Mens (resulting in http://wiki.powerdns.com/trac/changeset/3109), we discovered that NSD (both 3.2.15 and 4.0.0b4) compresses labels in RP content. As far as I can see, this is not allowed by RFC3597 section 4 paragraph 1/2. PowerDNS Recursor, like Unbound and BIND, now deals with this as 3597 section 4 paragraph 4 says we SHOULD. Nevertheless,

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

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

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 >

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, I just installed nsd 1.2.2, and found that it choked on the following zone file when parsing it as an IPv6 zone file, complaining about out-of-zone data on line 2: @ IN SOA ns.oryx.com. hostmaster.oryx.com. ( 2003091600 10800 3600 2592000 86400 ) 1 IN PTR localhost. Using it only under IPv4 worked. What I'm now using is

Hello, NSD 4.7.0 running on FreeBSD 13.X and serving DNSSEC signed zone (say mydomain.org) to the world. I've been approached by a customer with the request to include certain records into mydomain.org zone which will be resolvable only from their premises. I'm thinking to setup a pair of unbound instances, ask the customer to configure conditional forwarding for mydomain.org to those

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

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

Would prefer to continue to use my NSD/Unbound installs for most DNS (if not all) services. NSD is the authoritative server for the domain, and Unbound is the cache/resolver that the clients connect to. I'd like to not disturb this setup but I'll need the SRV records so that AD works. If the SRV records are fixed I suppose I could host them using NSD, then Samba wouldn't have to be

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:

Dear all, Could I use the tool "nsupdate" from the "dnsutils" package to update my zone/record in NSD ? http://docs.freebsd.org/doc/8.0-RELEASE/usr/share/doc/bind9/arm/man.nsupdate.html Thanks by advance.

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 lists in very large zonefiles. This was handy for things like IPv4/v6 PTR's and matching A/AAAA records for large dynamic hosts, etc. Does NSD support any type of range generation such at this? -- inoc.net!rblayzor XMPP:

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

On 03/10/2016 07:13 AM, Michael H wrote: > On 10/03/16 14:47, Leonardo Oliveira Ortiz wrote: >> Hello. >> >> I think Centos are affected, right? >> >> Some update from Centos? >> _______________________________________________ >> CentOS mailing list >> CentOS at centos.org >> https://lists.centos.org/mailman/listinfo/centos >> >

Can the Samba internal DNS be set as authoritative only (not a resolver)? Can the Samba DNS server be set as authoritative only for the SRV zones (_tcp, _udp _msdcs, _sites) and not the parent zone? Thanks, Chris

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

On Thu, Apr 7, 2016 at 11:00 AM, Sketch <smblist at rednsx.org> wrote: > My guess would be not much, because BIND9_DLZ exists and (mostly) gives you > the best of both worlds. If you want to use bind with MS DNS servers, then > you have to go that route, but it's not necessary with Samba 4 and > BIND9_DLZ. That's clear but I was thinking more of the analogous

As soon as RHEL does. On 03/10/2016 02:13 PM, Leonardo Oliveira Ortiz wrote: > CentOS will provide an update to fix it? > > ________________________________________ > De: centos-bounces at centos.org [centos-bounces at centos.org] em nome de Alice Wonder [alice at domblogger.net] > Enviado: quinta-feira, 10 de mar?o de 2016 15:31 > Para: centos at centos.org > Assunto: Re: