samba - Dec 2023 - bind crashes after samba upgrade

On Wed, 27 Dec 2023 11:39:41 -0500
Sonic <sonicsmith at gmail.com> wrote:
> On Wed, Dec 27, 2023 at 11:26?AM Rowland Penny via samba
> <samba at lists.samba.org> wrote:
> > What happened to 'include
"/etc/bind/named.conf.default-zones";' ?
> It always worked without them previously.
> 
> > See below about the keytab.
> 
> > You need a valid forwarder
> Forwarder is valid.
> 
> > Are you actually building Samba yourself ?
> > If not the entire path is wrong, if you are, it just a little bit
> > wrong. The path was changed from /.../.../samba/private/ to
> > /.../.../bind-dns/ where '/.../.../' is either
'/usr/local/' or
> > '/var/lib/' depending on a self compiled Samba or distro
packages.
> Yes, self compiled but the install puts nothing in /.../.../bind-dns/,
> however if I change to the internal backend and then back to bind the
> files show up in that new location. And I've edited the bind conf
> files with the new location with no change in the resulting crash on
> dlopen.
What are the full log messages when named starts and then crashes ?

Rowland

On Wed, Dec 27, 2023 at 11:52?AM Rowland Penny via samba
<samba at lists.samba.org> wrote:
> What are the full log messages when named starts and then crashes ?
I just have what is in the journal:
Instead of:
================================named[266]: Loading 'AD DNS Zone' using
driver dlopen
named[266]: samba_dlz: started for DN DC=my,DC=example,DC=com
named[266]: samba_dlz: starting configure
================================I get:
================================named[2785]: Loading 'AD DNS Zone' using
driver dlopen
systemd[1]: bind9.service: Main process exited, code=killed, status=11/SEGV
================================
I could try and enable some logging for next time.
I'm thinking it may be better to get 4.10 upgraded to 4.11 since the
database changes before attempting the jump to 4.18.

Thank you,
Chris