similar to: bind crashes after samba upgrade

On Sun, 24 Dec 2023 17:05:21 -0500 Sonic via samba <samba at lists.samba.org> wrote: > Finally biting the bullet and upgrading some old Samba servers. > This particular server is running 4.10.16 and as a first step I'm > attempting to upgrade it to 4.12.15 (I think I remember something > about 4.11.x not handling the upgrade properly). > > Samba seems to run OK but

25.12.2023 01:05, Sonic via samba : > Finally biting the bullet and upgrading some old Samba servers. > This particular server is running 4.10.16 and as a first step I'm > attempting to upgrade it to 4.12.15 (I think I remember something > about 4.11.x not handling the upgrade properly). This is most likely due to a bug in samba which is fixed in samba 4.18.0,

On 24.12.2023 23:05, Sonic via samba wrote: > Finally biting the bullet and upgrading some old Samba servers. > This particular server is running 4.10.16 and as a first step I'm > attempting to upgrade it to 4.12.15 (I think I remember something > about 4.11.x not handling the upgrade properly). > > Samba seems to run OK but bind9 will crash when loading the dns with dlopen:

My BIND9.6.0 on FreeBSD 6.2 works fine when I manually start with: root@ns2# named -4 -S 1024 -c /etc/namedb/named.conf But it won't start on boot and no error messages or log. And it won't start using rndc, it cause error message. Why does the error shows port 953 when I specified for port 53 in the config? rndc: connect failed: 127.0.0.1#953: connection refused Below are

CentOS 4.8, BIND 9.2.4 Hi All: I have a rather annoying problem with rndc which I have not been able to resolve despite much searching and many attempts to correct. When making changes to our DNS entries I have tried to use the following procedures: 1. Flush the cache buffers: rndc flush 2. Stop named: rndc stop 3. Delete the journal files: rm *.jnl 4. Edit the forward and/or

Hi all, I've set up a simple domain using Samba 4.4.2 from source under Ubuntu 16.04. I accepted the usual defaults and basically followed wiki.samba.org to the letter. The main thing is I'm using Samba's internal DNS and not Bind (Bind is not even installed on the system). In the log.samba file on the first DC I kept getting this: [2016/04/28 17:01:02.716292, 0]

Hi samba team ! I'm face with a new problem on a new Samba PDC install (Debian 9). I don't know why, but systemd run multiples "rndc reconfig" commands during the init script. So the bind9 log file show : -> A successful start -> A failed reconfig (samba_dlz Ignoring duplicate zone) at each boot/reboot. So I need to restart bind9 each time manually. I created a wrapper

I've done something a while back that has messed with my named.conf and prevents me from restarting named service normally... My problem... # service named restart Stopping named: [FAILED] Starting named: named: already running [FAILED] nothing gets logged in /var/log/messages obviously, I can do this to restart it... [root at

I just downloaded the bind-chroot rpm and looked into it with Archive manager (so I am lazy), and no files, just the chroot tree. I am assuming there is some script that Archive manager does not show, or I am just missing it, because the ROOTDIR= did get added to /etc/sysconfig/named (and the one in the bind rpm is without this line). Just interesting that if you chroot, you are expected to

In /var/named/chroot/etc there is no rndc.conf or named.conf. Where are they? Webmin built a named.conf, but it is missing many of the 'default' entries. And it did not set up the symbolic link to /etc I am trying to follow instructions at: http://www.wains.be/index.php/2007/02/04/centos-chroot-dns-with-bind/

Hello, I noticed in my logwatch file I have an error with my rndc key. I could 'play' around with it and may fix it but most likey just hose things up. I think I see the problem but not 100% sure. I think the key file has 3 different names. Here's the error: **Unmatched Entries** /etc/named.conf:23: couldn't find key 'rndckey' for use with command channel

On 4/28/2016 1:05 PM, Rowland penny wrote: > On 28/04/16 17:21, Wayne Merricks wrote: >> Hi all, >> >> I've set up a simple domain using Samba 4.4.2 from source under >> Ubuntu 16.04. >> >> I accepted the usual defaults and basically followed wiki.samba.org >> to the letter. The main thing is I'm using Samba's internal DNS and >>

Yesterday I had an issue with Samba v 4.13.0. Went to backup and discovered backup computer has a drive failure and backup is gone. Only resort is to rebuild the DC. I cannot figure out why bind9 will not "host -t SRV _ldap._ tcp.ad.dtntwk.work." or "host -t SRV _kerberos._udp.ad.dtntwk.work." root at dc1:~# host -t SRV _ldap._tcp.subdom.example.com. >

I recently upgraded my name server to CentOs 4.4 from CentOs 4.3 and bind was one of the many packages upgraded. I get the following message when performing an rndc reload " rndc reload rndc: connection to remote host closed This may indicate that the remote server is using an older version of the command protocol, this host is not authorized to connect, or the key is invalid." which

Hi list, here is what happened: today I noticed some resolution's problems on my network. I did a "service named status" and here was the output: # /etc/init.d/named status rndc: connection to remote host closed This may indicate that the remote server is using an older version of the command protocol, this host is not authorized to connect, or the key is invalid. In the

> > I repeat, Bind 9.12.x is unsupported at this time, just because it > worked once is no reason to use it. It may have nothing to do with your > problem, but using a supported Bind version will rule it out. Ok. :) I'll reinstall using supported version 9.11.3-2 OK, your server, but I think you should be aware that I have been using > Bind9 with Samba since December 2012

I am reading: https://www.centos.org/docs/5/html/Deployment_Guide-en-US/s1-bind-rndc.html I have bind installed and default config running. I have not applied my customizations yet. The first step I am taking is getting rndc.key created. So reading the guide I am trying to run (while logged in as root, and in /etc): dnssec-keygen -a hmac-md5 -b 256 -n HOST rndc.key The system is just

Mandi! L.P.H. van Belle via samba In chel di` si favelave... > > c) seems to use some ''random'' AD DNS, not the one in the site, for > > example. > Yes that is correct. ( The DC Locator Process does that ) > If you dont want that, you can assign by GPO a preffered server. > You can set it as preffered server per site in the GPO. ( note, a pc needs 2

hi wile i am running the command rndc reload i am getting the error rndc: connect failed: 127.0.0.1#953: connection refuse any one can suggest where i am doing wrong this is my rndc.conf key "rndckey" { algorithm hmac-md5; secret "fKZfrqGy9VOPOLA3pgDACA=="; }; options { default-key "rndckey"; default-server 127.0.0.1;

> > Hmm, bind 9.12.x isn't supported yet. He works with "dlopen /usr/lib/x86_64-linux-gnu/samba/bind9/dlz_bind9_11.so" without problems, at first. include "/etc/bind/rndc.key"; > controls { > inet 127.0.0.1 allow { localhost; } keys { rndc-key;}; > }; > You do not need the four lines above Ok, but if I leave it, does not have problems