similar to: tinydns exceeds "holdoff time" on startup under CentOS 7

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

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

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

I'm workign to setup Samba4 and my current centos server deployment uses TinyDNS/DNSCache for the DNS. Understanding that it is best to use Sambas internal DNS for AD, I'm wondering how others are doing DNS? I really don't want to use BIND. Should my DHCP server send ddns updates to Samba's internal DNS for client leases? Thanks, -- Greg J. Zartman Board Member Koozali

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

Use BIND. How the times have changed. :-) PS: I'm also curious for a solution.. for when djbnostalgia hits me. Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "Boris Epstein" <borepstein at gmail.com> > To: "CentOS mailing list" <centos at centos.org> > Sent: Tuesday, 13 January,

On 07/05/2019 01:43 PM, Rowland penny via samba wrote: > On 05/07/2019 18:59, Robert A Wooldridge via samba wrote: >> Is it necessary to use Samba's DNS when configuring as a domain >> controller?? Can a DNS server be used on a different machine? >> > The dns server must be authoritative for the AD dns domain but you do > not need to use the Samba internal dns

Thanks for getting back with the "solution". You might want to give that bugzilla entry a jolt, it's been stagnating since last year. :-) Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "Boris Epstein" <borepstein at gmail.com> > To: "CentOS mailing list" <centos at

Hi there, I've been a happy djbdns+tinydns user for many, many years. I want to keep using it, so answers of the form "bletch! Use ISC BIND the way BSD intended" will be ignored :-) Having said that, one annoying consequence of my transition some time ago to using ntpd, rather than just setting the clock once-off with ntpdate as I used to, is that the /etc/rc.d mechanism starts

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

On 07/05/2019 02:11 PM, Rowland penny via samba wrote: > On 05/07/2019 20:03, Robert A Wooldridge via samba wrote: >> On 07/05/2019 01:55 PM, Rowland penny via samba wrote: >>> I currently run tinydns and dnscache on my proxy machine.? I was >>> hoping to keep that going.? I have a Windows Server2004 doing DC >>> work right now.? Need to update that.

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

List: Sorry for posting to this list but could not find step by step instructions anywhere nor get any concerned list to respond. Newbie to DNS technicals but can work with instructions if given in ./configure for complete idiots ;-) 1. I have taken a static IP from my ISP 203.134.221.162 and the ISP has put up an entry in APNIC whois (please check the same)...to me it seems incomplete, as it

I am having two problems, possibly related, while performing pre-deployment testing of a Samba/OpenLDAP PDC with data that was vampired from an NT4 PDC. The Samba server fails to become a local master browser, and password change attempts (from a Windows client) fail. I followed Samba-Guide/ntmigration.html (taking some liberties with various items of configuration), ending with step #19.

Hi all, Currently at work we use a commercial product called "Gnatbox", which, I believe, is a BSD derivative running on a floppy disk. They have a pretty UI and all, but I''d feel much safer/happier with a GNU/Linux box and Shorewall doing the same thing. In fact, I''m doing something very close to this at home using Openwrt and Shorewall on my WRT54G router, but I

On 07/05/2019 01:55 PM, Rowland penny via samba wrote: > I currently run tinydns and dnscache on my proxy machine.? I was > hoping to keep that going.? I have a Windows Server2004 doing DC work > right now.? Need to update that. >> >> -- >> Bob Wooldridge >> > You can run a caching nameserver that forwards your AD dns zones to > your AD DC, but you can

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

Hello Wouter, We used tinydns for many years. After migration to nsd3 we miss only one feature present in tinydns only: tinydns may switch addresses by decreasing the ttl for old data and serve new data starting from a fixed timestamp. http://cr.yp.to/djbdns/tinydns-data.html: You may include a timestamp on each line. If ttl is nonzero (or omitted), the timestamp is a starting time for the

i386 Transparent paravirtualization patch #1. Add support for interrupt holdoff to the entry.S fault and syscall paths. This is a straightforward macro-ization for the default sub-architecture. Note that CLI, STI and IRET may be called with non-flat segments because guest %ds and %es segments are live at the time. Any alternative implementation (such as a virtual interrupt mask) is required to

i386 Transparent paravirtualization patch #1. Add support for interrupt holdoff to the entry.S fault and syscall paths. This is a straightforward macro-ization for the default sub-architecture. Note that CLI, STI and IRET may be called with non-flat segments because guest %ds and %es segments are live at the time. Any alternative implementation (such as a virtual interrupt mask) is required to