[Samba] Problems joining station in domain

L.P.H. van Belle belle at bazuin.nl
Thu Aug 29 06:34:10 UTC 2019


Hai Marcio,

I looks like your now at to point you can try to join yes. 

Disable this line : /etc/bind/named.conf.local 
Now you are able to join.

I dont know the version your using now, but you can find the file named.conf 
After the join or here 
/var/lib/samba/bind-dns/
Or here
/var/lib/samba/private/


Greetz, 

Louis



> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens 
> Marcio Demetrio Bacci via samba
> Verzonden: woensdag 28 augustus 2019 22:58
> Aan: Rowland penny
> CC: sambalist
> Onderwerp: Re: [Samba] Problems joining station in domain
> 
> Hi,
> 
> When I restarted my DNS Bind I noticed that it isn't working, 
> as follows:
> 
> /etc/init.d/bind9 status
> ??? bind9.service - BIND Domain Name Server
>    Loaded: loaded (/lib/systemd/system/bind9.service; enabled; vendor
> preset: enabled)
>   Drop-In: /etc/systemd/system/bind9.service.d
>            ??????override.conf
>    Active: failed (Result: exit-code) since Wed 2019-08-28 
> 17:25:59 -03;
> 21min ago
>      Docs: man:named(8)
>   Process: 776 ExecStop=/usr/sbin/rndc stop (code=exited, 
> status=1/FAILURE)
>   Process: 752 ExecStart=/usr/sbin/named -f $OPTIONS (code=exited,
> status=1/FAILURE)
>  Main PID: 752 (code=exited, status=1/FAILURE)
> 
> ago 28 17:25:59 samba4-dc3 named[752]: using up to 4096 sockets
> ago 28 17:25:59 samba4-dc3 named[752]: loading configuration from
> '/etc/bind/named.conf'
> ago 28 17:25:59 samba4-dc3 named[752]: 
> /etc/bind/named.conf.local:12: open:
> /var/lib/samba/private/named.conf: file not found
> ago 28 17:25:59 samba4-dc3 named[752]: loading configuration: 
> file not found
> ago 28 17:25:59 samba4-dc3 named[752]: exiting (due to fatal error)
> ago 28 17:25:59 samba4-dc3 systemd[1]: bind9.service: Main 
> process exited,
> code=exited, status=1/FAILURE
> ago 28 17:25:59 samba4-dc3 rndc[776]: rndc: connect failed: 
> 127.0.0.1#953:
> connection refused
> ago 28 17:25:59 samba4-dc3 systemd[1]: bind9.service: Control process
> exited, code=exited status=1
> ago 28 17:25:59 samba4-dc3 systemd[1]: bind9.service: Unit 
> entered failed
> state.
> ago 28 17:25:59 samba4-dc3 systemd[1]: bind9.service: Failed 
> with result
> 'exit-code'.
> 
> Should I join DC in the domain now, or I have to correct these issues
> before?
> 
> Regards,
> 
> Márcio Bacci
> 
> Em qua, 28 de ago de 2019 às 16:09, Rowland penny via samba <
> samba at lists.samba.org> escreveu:
> 
> > On 28/08/2019 19:51, Marcio Demetrio Bacci wrote:
> > > Hi,
> > >
> > > I am setting up Bind_DLZ on a new DC that isn't in the domain yet.
> > >
> > > I have followed Louis's guidelines for setting up 
> Bind9_DLZ, but the
> > > above files must be passed in the settings, however they 
> do not exist
> > > in my installation.
> > I see, as you haven't started bind9 yet, this doesn't matter, just
> > create the bind conf files, join to the domain with
> > '--dns-backend=BIND9_DLZ' and the required files will be 
> created, you
> > can start Bind9 now.
> > >
> > > After I join the new server as DC with Bind9_DLZ, I 
> intend to migrate
> > > from Samba Internal DNS Server to the BIND9_DLZ.
> > >
> > If you join as above, you will have migrated ;-)
> >
> > Rowland
> >
> >
> >
> > --
> > To unsubscribe from this list go to the following URL and read the
> > instructions:  https://lists.samba.org/mailman/options/samba
> >
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
> 
> 




More information about the samba mailing list