similar to: SERVFAIL <=> NXDOMAIN

Recently I'm getting these errors on my slave when adding new domains: Sep 26 13:48:27 hosting named[1668]: zone wholesaletvtime.com/IN: refresh: unexpected rcode (SERVFAIL) from master 207.218.174.4#53 The master/slave transfers work for the other 1000+ domains that I have, just not the handful of new ones that I just added after the CentOS 4.3 -> 4.4 upgrade. I regenerated the

Hello, I have dns zone domain.com configured on nsd server. If a try #dig axfr @localhost domain.com then i receive correct answer, but if i try #dig a @localhost domain.com then i received nothing but should be 127.0.0.1 How can i troubleshoot this problem? output: [root at ns1 ~]# dig axfr @localhost domain.com ; <<>> DiG 9.8.3-P1-RedHat-9.8.3-2.P1.fc15 <<>> axfr

I just set up a CentOS 5.2 system with bind9 (9.3.4-6.0.1.P1.el5) and I'm running up against a problem that seems to be related to SELinux. If I set named_disable_trans to 1, everything works as expected, but if I leave it enabled the server will only give me data for the zones for which it is authoritative. For external sites it returns a ServFail error. This is with nslookup and dig. If I

I have just set up a new AD and am having a little success with it, but DNS resolution is a little slow. I'm looking into why that is and tried an ns lookup for google.com and got the answer SERVFAIL on my AD server. The query was then passed to my next nameserver (google's own dns), which handled the query. Is this correct behaviour? I've not seen SERVFAIL before itadmin at

I think it?s the cache. When you where sleeping the cache got updated. But I can be wrong Philip > On 5 Sep 2020, at 12:35, Rowland penny via samba <samba at lists.samba.org> wrote: > > On 05/09/2020 09:53, Peter Pollock via samba wrote: >> I have just set up a new AD and am having a little success with it, but DNS >> resolution is a little slow. >> >>

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

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 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 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 list, We are observing strange behavior of nsd v3.2.9 acting as slave DNS server. The environment is set up as follows: 0. We are using 172.16.0.0/16 subnet; 1. Primary Master server at 172.16.100.114; 2. Slave server at 172.16.100.115. The config file is in /etc/nsd-dns-slave.conf; 3. There may be also other Master servers im the given subnet. Now I want to permit DNS NOTIFY messages to

Hello World, I am trying to build NSD4 on Debian Squeeze and I get the following errors when running `make`. ``` $ pwd /home/wiz/src/nsd/tags/NSD_4_0_0_imp_5 $ make [... output omitted ...] gcc -g -O2 -o nsd-checkconf answer.o axfr.o buffer.o configlexer.o configparse acket.o query.o rbtree.o radtree.o rdata.o region-allocator.o tsig.o tsig-opens 4_pton.o b64_ntop.o -lcrypto configparser.o: In

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have set up Samba-3.0.11 to retrive account information from W2k server via winbind, and it works. But is takes about 10 sec. to retrive the information. I have dumped some traffic from the request, and it looks like this: A lot of these: 21:21:55.133423 172.20.3.131.1077 > 172.20.3.130.137: NBT UDP PACKET(137): QUERY; REQUEST; UNICAST

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

Hi, I found a reproducible seg fault with a DNSSEC signed zone and overlapping config. I'm running NSD 4.10.1. Here's how to reproduce. 2 zones in nsd.conf: zone: name: "foo.com." zonefile: "/zones/foo.com.zone.signed" zone: name: "bar.foo.com." zonefile: "/zones/bar.foo.com.zone" Zone files:

Hi all, I'm running NSD 4.9.1 on OpenBSD 7.6. I recently upgraded from OpenBSD 7.5, which I believe had NSD 4.8.0 in base, and did not see this behavior prior. When I try to reload a zone using nsd-control, I am seeing an error message in my logfile: "error: reload: old-main quit during quit sync" This error does not appear to happen every time I run reload, but it does get

Hi Andreas, On 18/04/2025 23:28, A. Schulze via nsd-users wrote: > I added #437 to my build. It works, somehow... > > I cannot imagine a scenario for any (resolver?) software to implicitly > send a SOA probe over UDP to port 853 / not port 53 > Could you clarify this, please? Unbound is an example when configured with auth zones, it will send the SOA prove over UDP before

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, 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".