similar to: Featurerequest for nsd4

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

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

Hello, Lutz Donnerhacke implemented DNS-Dampening. http://lutz.donnerhacke.de/eng/Blog/DNS-Dampening The implementation is available as patch for BIND9 only. He told me that there is an other method preferred by the nsd developer. It's called "Response Rate Limiting". May one describe the idea behind rate limiting and compare it with Lutz' solution? Thanks. -- Andreas

Hi, I have a query regarding running a manual update of nsd via: # nsdc update My NSD server is accepting notifications from two servers. From my nsd.conf: # master 1 allow-notify: X.X.X.X NOKEY request-xfr: AXFR X.X.X.X NOKEY # master 2 allow-notify: Y.Y.Y.Y NOKEY request-xfr: AXFR Y.Y.Y.Y NOKEY Are both servers sequentially queried each time

Hi I'm starting a migration from NSD 3 -> 4. I note in @src ./contrib/ that an init.d is still provided. Are there any systemd service files, etc. available/documented/recommended yet? darx

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

hi, after i test nsd i find the following. if i use this in a zone file: $ORIGIN example.com. CNAME www www CNAME x x A 1.2.3.4 then it's excepted by nsd what's more give the proper result. if the slave is nsd than there is no problem, while if the slave is bind i've got the following error:

Good morning: We're about to start moving our public DNS to in-house managed servers. My first thought was "Linux + BIND" and we're done. Someone in another business unit's IT dept. has suggested tinydns be used. >From what I could find, it looks like this software hasn't really had any community drive behind it in a while. The latest RPMs on rpmforge are for red hat

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

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

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!

Hello listmates, Somehow or other my DNS services that are part of the ndjbdns-1.06-1.el7.x86_64 package would not start properly at startup. When I then start them up using systemctl: systemctl start dnscache systemctl start tinydns they start just fine. >From the log I got the following for tinydns: Oct 24 15:01:43 ns99 tinydns[1867]: tinydns: version 1.06: starting: Oct-24 2014 15:01:43

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

Hello all, We have put a DNS server online running DJBDNS v1.06 (ndjbdns-1.06-1.el6.x86_64) on a 64-bit CentOS 6.6 server. We have done some limited testing on the machine which it passed - i.e., dnscache was talking to tinydns, the queries went through fine, etc. As soon as we put it online subjecting it to live load the following happened: 1) Within a short time period (about a minute) the

Hi I've got rsync setup to replicate DNS for an irc network I help run. I'm the primary DNS, so I use the rsync client to connect to a friend running another DNS server, and he has the rsync daemon setup. the conf is as follows log file = /root/rsync.log [tinydns] path = /etc/tinydns/root/ use chroot = no max connections = 2 read only = false list = false uid = root

Hi all, tinydns starts up fine, selinux reports no issues (now after a day of clearing errors). If I turn selinux back to permissive in /etc/sysconfig/selinux, and reboot, tinydns responds to queries. If I turn selinux back to enforcing and reboot, tinydns does not respond. Monitoring /var/log/messages shows no errors from iptables/shorewall or selinux. The only way I can find an error is

Is there a tinydns or dns wizard that could give me some hints, please? I am setting up and testing tinydns, but have some problems figuring out how to route. I do get dnscache to listen on tinydns. Also I do not understand why it will not answer the given ip (127.0.0.1) to the name server. 1. Both services are up running and seems to be working fine, so why no reply, (on the first

Lucian, So far here is the best we could find out: https://bugzilla.redhat.com/show_bug.cgi?id=1084747 Testing to see if this is the solution; so far it seems to be. Cheers, Boris. On Tue, Jan 13, 2015 at 2:49 PM, Nux! <nux at li.nux.ro> wrote: > Use BIND. How the times have changed. :-) > > PS: I'm also curious for a solution.. for when djbnostalgia hits me. > >

Hi, I'm testing: $ sudo nsd-control status version: 4.0.1 verbosity: 2 I found a loop problem with this record: * IN CNAME none ("none" means no matching record in zone and therefore match * again) Queries that use "* CNAME" will result in a loop. The response will use TCP and will be limited to 65k bytes $ dig @127.0.0.1 sdfgsfg.test.com ;; Truncated,