L.P.H. van Belle
2017-Jan-20 14:21 UTC
[Samba] DNS Update not working after update to 4.5.3
I suspect a zone overlap. Did you add an extra zone manualy in bind? Or something like this... You added : Zone1.Domain.TLD and then Domain.TLD But then with the reverse zones. Because this :> Jan 20 13:58:09 samba02 named[10811]: zone 2.168.192.in-addr.arpa/NONE: > has no NS recordsDoes not look likes the samba_DLZ log lines but a pure bind log line. Review you bind config and remove any manualy added zones. Greetz, Louis> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Dirk Laurenz via > samba > Verzonden: vrijdag 20 januari 2017 13:58 > Aan: Marc Muehlfeld; samba at lists.samba.org > Onderwerp: Re: [Samba] DNS Update not working after update to 4.5.3 > > Hi, > > > i tried this hint and after restart of bind9: > > > Jan 20 13:58:08 samba02 named[10811]: Loading 'AD DNS Zone' using driver > dlopen > Jan 20 13:58:09 samba02 named[10811]: samba_dlz: started for DN > DC=local,DC=laurenz,DC=ws > Jan 20 13:58:09 samba02 named[10811]: samba_dlz: starting configure > Jan 20 13:58:09 samba02 named[10811]: zone 2.168.192.in-addr.arpa/NONE: > has no NS records > Jan 20 13:58:09 samba02 named[10811]: samba_dlz: Failed to configure > zone '2.168.192.in-addr.arpa' > Jan 20 13:58:09 samba02 named[10811]: loading configuration: bad zone > > hmm bad luck... why got the PTR Zone lost....? > > > Dirk > > > Am 18.01.2017 um 18:03 schrieb Marc Muehlfeld: > > Hi Dirk, > > > > Am 18.01.2017 um 08:51 schrieb Dirk Laurenz via samba: > >> [2017/01/18 08:31:18.113146, 0] > >> ../source4/dsdb/dns/dns_update.c:290(dnsupdate_nameupdate_done) > >> > >> ../source4/dsdb/dns/dns_update.c:290: Failed DNS update - with error > code > >> 110 > > Do you run the BIND9_DLZ or Internal_DNS back end? > > > > If it's BIND: > > > https://wiki.samba.org/index.php/BIND9_DLZ_DNS_Back_End#Reconfiguring_the_ > BIND9_DLZ_Back_End > > > > > > Regards, > > Marc > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba
ok - i will try this, means before starting: will remove all reverse dns zones? correct? i only add dns zones via windows dns mgmt and only outside bind... bind config is like in wiki.samba.org grep samba /etc/bind/* /etc/bind/named.conf.local:include "/var/lib/samba/private/named.conf"; /etc/bind/named.conf.options: tkey-gssapi-keytab "/var/lib/samba/private/dns.keytab"; other things a default debian.... Am 20.01.2017 um 15:21 schrieb L.P.H. van Belle via samba:> I suspect a zone overlap. > Did you add an extra zone manualy in bind? > > Or something like this... You added : > Zone1.Domain.TLD and then > Domain.TLD > > But then with the reverse zones. > > Because this : > >> Jan 20 13:58:09 samba02 named[10811]: zone 2.168.192.in-addr.arpa/NONE: >> has no NS records > Does not look likes the samba_DLZ log lines but a pure bind log line. > Review you bind config and remove any manualy added zones. > > > > Greetz, > > Louis > > > > >> -----Oorspronkelijk bericht----- >> Van: samba [mailto:samba-bounces at lists.samba.org] Namens Dirk Laurenz via >> samba >> Verzonden: vrijdag 20 januari 2017 13:58 >> Aan: Marc Muehlfeld; samba at lists.samba.org >> Onderwerp: Re: [Samba] DNS Update not working after update to 4.5.3 >> >> Hi, >> >> >> i tried this hint and after restart of bind9: >> >> >> Jan 20 13:58:08 samba02 named[10811]: Loading 'AD DNS Zone' using driver >> dlopen >> Jan 20 13:58:09 samba02 named[10811]: samba_dlz: started for DN >> DC=local,DC=laurenz,DC=ws >> Jan 20 13:58:09 samba02 named[10811]: samba_dlz: starting configure >> Jan 20 13:58:09 samba02 named[10811]: zone 2.168.192.in-addr.arpa/NONE: >> has no NS records >> Jan 20 13:58:09 samba02 named[10811]: samba_dlz: Failed to configure >> zone '2.168.192.in-addr.arpa' >> Jan 20 13:58:09 samba02 named[10811]: loading configuration: bad zone >> >> hmm bad luck... why got the PTR Zone lost....? >> >> >> Dirk >> >> >> Am 18.01.2017 um 18:03 schrieb Marc Muehlfeld: >>> Hi Dirk, >>> >>> Am 18.01.2017 um 08:51 schrieb Dirk Laurenz via samba: >>>> [2017/01/18 08:31:18.113146, 0] >>>> ../source4/dsdb/dns/dns_update.c:290(dnsupdate_nameupdate_done) >>>> >>>> ../source4/dsdb/dns/dns_update.c:290: Failed DNS update - with error >> code >>>> 110 >>> Do you run the BIND9_DLZ or Internal_DNS back end? >>> >>> If it's BIND: >>> >> https://wiki.samba.org/index.php/BIND9_DLZ_DNS_Back_End#Reconfiguring_the_ >> BIND9_DLZ_Back_End >>> >>> Regards, >>> Marc >> >> -- >> To unsubscribe from this list go to the following URL and read the >> instructions: https://lists.samba.org/mailman/options/samba > >
hmm, just a guess: i have two reverse lookup zones: 192.168.2.x 192.168.6.x defined. should i define 192.168.x.x instead? Am 20.01.2017 um 15:21 schrieb L.P.H. van Belle via samba:> I suspect a zone overlap. > Did you add an extra zone manualy in bind? > > Or something like this... You added : > Zone1.Domain.TLD and then > Domain.TLD > > But then with the reverse zones. > > Because this : > >> Jan 20 13:58:09 samba02 named[10811]: zone 2.168.192.in-addr.arpa/NONE: >> has no NS records > Does not look likes the samba_DLZ log lines but a pure bind log line. > Review you bind config and remove any manualy added zones. > > > > Greetz, > > Louis > > > > >> -----Oorspronkelijk bericht----- >> Van: samba [mailto:samba-bounces at lists.samba.org] Namens Dirk Laurenz via >> samba >> Verzonden: vrijdag 20 januari 2017 13:58 >> Aan: Marc Muehlfeld; samba at lists.samba.org >> Onderwerp: Re: [Samba] DNS Update not working after update to 4.5.3 >> >> Hi, >> >> >> i tried this hint and after restart of bind9: >> >> >> Jan 20 13:58:08 samba02 named[10811]: Loading 'AD DNS Zone' using driver >> dlopen >> Jan 20 13:58:09 samba02 named[10811]: samba_dlz: started for DN >> DC=local,DC=laurenz,DC=ws >> Jan 20 13:58:09 samba02 named[10811]: samba_dlz: starting configure >> Jan 20 13:58:09 samba02 named[10811]: zone 2.168.192.in-addr.arpa/NONE: >> has no NS records >> Jan 20 13:58:09 samba02 named[10811]: samba_dlz: Failed to configure >> zone '2.168.192.in-addr.arpa' >> Jan 20 13:58:09 samba02 named[10811]: loading configuration: bad zone >> >> hmm bad luck... why got the PTR Zone lost....? >> >> >> Dirk >> >> >> Am 18.01.2017 um 18:03 schrieb Marc Muehlfeld: >>> Hi Dirk, >>> >>> Am 18.01.2017 um 08:51 schrieb Dirk Laurenz via samba: >>>> [2017/01/18 08:31:18.113146, 0] >>>> ../source4/dsdb/dns/dns_update.c:290(dnsupdate_nameupdate_done) >>>> >>>> ../source4/dsdb/dns/dns_update.c:290: Failed DNS update - with error >> code >>>> 110 >>> Do you run the BIND9_DLZ or Internal_DNS back end? >>> >>> If it's BIND: >>> >> https://wiki.samba.org/index.php/BIND9_DLZ_DNS_Back_End#Reconfiguring_the_ >> BIND9_DLZ_Back_End >>> >>> Regards, >>> Marc >> >> -- >> To unsubscribe from this list go to the following URL and read the >> instructions: https://lists.samba.org/mailman/options/samba > >
On Mon, 23 Jan 2017 14:34:28 +0100 Dirk Laurenz via samba <samba at lists.samba.org> wrote:> hmm, just a guess: > > i have two reverse lookup zones: > > 192.168.2.x > > 192.168.6.x > > defined. should i define 192.168.x.x instead? >This would probably be better than the two zones, but are your windows clients setup to update the reverse zone ? Rowland
Hi, i reduced to one reverse dns zone (192.168.x.x.) same error when converting internal to bind_dlz Jan 23 14:55:39 samba01 named[3279]: Loading 'AD DNS Zone' using driver dlopen Jan 23 14:55:40 samba01 named[3279]: samba_dlz: started for DN DC=local,DC=laurenz,DC=ws Jan 23 14:55:40 samba01 named[3279]: samba_dlz: starting configure Jan 23 14:55:40 samba01 named[3279]: samba_dlz: configured writeable zone '168.192.in-addr.arpa' Jan 23 14:55:40 samba01 named[3279]: zone local.laurenz.ws/NONE: has no NS records Jan 23 14:55:40 samba01 named[3279]: samba_dlz: Failed to configure zone 'local.laurenz.ws' Jan 23 14:55:40 samba01 named[3279]: loading configuration: bad zone Jan 23 14:55:40 samba01 named[3279]: exiting (due to fatal error) Jan 23 14:55:40 samba01 systemd[1]: bind9.service: main process exited, code=exited, status=1/FAILURE Jan 23 14:55:40 samba01 rndc[3305]: rndc: connect failed: 127.0.0.1#953: connection refused Jan 23 14:55:40 samba01 systemd[1]: bind9.service: control process exited, code=exited status=1 Jan 23 14:55:40 samba01 systemd[1]: Unit bind9.service entered failed state. that worked before...no bind complains about my forward lookup zone...? Am 23.01.2017 um 14:34 schrieb Dirk Laurenz via samba:> hmm, just a guess: > > i have two reverse lookup zones: > > 192.168.2.x > > 192.168.6.x > > defined. should i define 192.168.x.x instead? > > > > Am 20.01.2017 um 15:21 schrieb L.P.H. van Belle via samba: >> I suspect a zone overlap. >> Did you add an extra zone manualy in bind? >> >> Or something like this... You added : >> Zone1.Domain.TLD and then >> Domain.TLD >> >> But then with the reverse zones. >> >> Because this : >> >>> Jan 20 13:58:09 samba02 named[10811]: zone 2.168.192.in-addr.arpa/NONE: >>> has no NS records >> Does not look likes the samba_DLZ log lines but a pure bind log line. >> Review you bind config and remove any manualy added zones. >> >> >> >> Greetz, >> >> Louis >> >> >> >> >>> -----Oorspronkelijk bericht----- >>> Van: samba [mailto:samba-bounces at lists.samba.org] Namens Dirk >>> Laurenz via >>> samba >>> Verzonden: vrijdag 20 januari 2017 13:58 >>> Aan: Marc Muehlfeld; samba at lists.samba.org >>> Onderwerp: Re: [Samba] DNS Update not working after update to 4.5.3 >>> >>> Hi, >>> >>> >>> i tried this hint and after restart of bind9: >>> >>> >>> Jan 20 13:58:08 samba02 named[10811]: Loading 'AD DNS Zone' using >>> driver >>> dlopen >>> Jan 20 13:58:09 samba02 named[10811]: samba_dlz: started for DN >>> DC=local,DC=laurenz,DC=ws >>> Jan 20 13:58:09 samba02 named[10811]: samba_dlz: starting configure >>> Jan 20 13:58:09 samba02 named[10811]: zone 2.168.192.in-addr.arpa/NONE: >>> has no NS records >>> Jan 20 13:58:09 samba02 named[10811]: samba_dlz: Failed to configure >>> zone '2.168.192.in-addr.arpa' >>> Jan 20 13:58:09 samba02 named[10811]: loading configuration: bad zone >>> >>> hmm bad luck... why got the PTR Zone lost....? >>> >>> >>> Dirk >>> >>> >>> Am 18.01.2017 um 18:03 schrieb Marc Muehlfeld: >>>> Hi Dirk, >>>> >>>> Am 18.01.2017 um 08:51 schrieb Dirk Laurenz via samba: >>>>> [2017/01/18 08:31:18.113146, 0] >>>>> ../source4/dsdb/dns/dns_update.c:290(dnsupdate_nameupdate_done) >>>>> >>>>> ../source4/dsdb/dns/dns_update.c:290: Failed DNS update - with >>>>> error >>> code >>>>> 110 >>>> Do you run the BIND9_DLZ or Internal_DNS back end? >>>> >>>> If it's BIND: >>>> >>> https://wiki.samba.org/index.php/BIND9_DLZ_DNS_Back_End#Reconfiguring_the_ >>> >>> BIND9_DLZ_Back_End >>>> >>>> Regards, >>>> Marc >>> >>> -- >>> To unsubscribe from this list go to the following URL and read the >>> instructions: https://lists.samba.org/mailman/options/samba >> >> > >
L.P.H. van Belle
2017-Jan-23 14:41 UTC
[Samba] DNS Update not working after update to 4.5.3
Hai, Seeing :> Jan 23 14:55:40 samba01 named[3279]: samba_dlz: configured writeable> zone '168.192.in-addr.arpa'> Jan 23 14:55:40 samba01 named[3279]: zone local.laurenz.ws/NONE: has no> NS records> Jan 23 14:55:40 samba01 named[3279]: samba_dlz: Failed to configure zone> 'local.laurenz.ws'Normaly you should see first the local.laurenz.ws zone with samba_dlz. So i think that this zone : local.laurenz.ws, is in bind_flat files ( not samba_dlz backend ) and this is correct samba_dlz: configured writeable zone '168.192.in-addr.arpa' Or as told, you created an dns record in 'domain.tld’, Which should be made in 'main.domain.tld' Use CNAME in domain.tld to link to host inside main.domain.tld. Then it works fine. Now this also applies for the reverse zones. If your using 192.168.0.0/16 then yes, your reverse : '168.192.in-addr.arpa is correct. If your not using a full /16 range, but a normal /24 then your reverse should be '0.168.192.in-addr.arpa’ You can use '168.192.in-addr.arpa’ but the use only one reverse zone. And i think your primary zone isnt in samba_DLZ. So can you post your bind config ( complete please, anonymize if needed ) This is my output as reference. Jan 23 15:25:25 rtd-dc1 named[4942]: ---------------------------------------------------- Jan 23 15:25:25 rtd-dc1 named[4942]: BIND 9 is maintained by Internet Systems Consortium, Jan 23 15:25:25 rtd-dc1 named[4942]: Inc. (ISC), a non-profit 501(c)(3) public-benefit Jan 23 15:25:25 rtd-dc1 named[4942]: corporation. Support and training for BIND 9 are Jan 23 15:25:25 rtd-dc1 named[4942]: available at https://www.isc.org/support Jan 23 15:25:25 rtd-dc1 named[4942]: ---------------------------------------------------- Jan 23 15:25:25 rtd-dc1 named[4942]: adjusted limit on open files from 4096 to 1048576 Jan 23 15:25:25 rtd-dc1 named[4942]: found 2 CPUs, using 2 worker threads Jan 23 15:25:25 rtd-dc1 named[4942]: using 2 UDP listeners per interface Jan 23 15:25:25 rtd-dc1 named[4942]: using up to 4096 sockets Jan 23 15:25:25 rtd-dc1 named[4942]: loading configuration from '/etc/bind/named.conf' Jan 23 15:25:25 rtd-dc1 named[4942]: reading built-in trusted keys from file '/etc/bind/bind.keys' Jan 23 15:25:25 rtd-dc1 named[4942]: using default UDP/IPv4 port range: [1024, 65535] Jan 23 15:25:25 rtd-dc1 named[4942]: using default UDP/IPv6 port range: [1024, 65535] Jan 23 15:25:25 rtd-dc1 named[4942]: listening on IPv4 interface lo, 127.0.0.1#53 Jan 23 15:25:25 rtd-dc1 named[4942]: listening on IPv4 interface eth0, 192.168.123.211#53 Jan 23 15:25:25 rtd-dc1 named[4942]: generating session key for dynamic DNS Jan 23 15:25:25 rtd-dc1 named[4942]: sizing zone task pool based on 5 zones Jan 23 15:25:25 rtd-dc1 named[4942]: Loading 'AD DNS Zone' using driver dlopen Jan 23 15:25:25 rtd-dc1 named[4942]: samba_dlz: started for DN DC=office,DC=domain,DC=tld Jan 23 15:25:25 rtd-dc1 named[4942]: samba_dlz: starting configure Jan 23 15:25:25 rtd-dc1 named[4942]: samba_dlz: configured writeable zone '123.168.192.in-addr.arpa' Jan 23 15:25:25 rtd-dc1 named[4942]: samba_dlz: configured writeable zone '0.123.10.in-addr.arpa' Jan 23 15:25:25 rtd-dc1 named[4942]: samba_dlz: configured writeable zone '1.123.10.in-addr.arpa' Jan 23 15:25:25 rtd-dc1 named[4942]: samba_dlz: configured writeable zone '2.123.10.in-addr.arpa' Jan 23 15:25:25 rtd-dc1 named[4942]: samba_dlz: configured writeable zone '3.123.10.in-addr.arpa' Jan 23 15:25:25 rtd-dc1 named[4942]: samba_dlz: configured writeable zone '4.123.10.in-addr.arpa' Jan 23 15:25:25 rtd-dc1 named[4942]: samba_dlz: configured writeable zone 'main.domain.tld' Jan 23 15:25:25 rtd-dc1 named[4942]: samba_dlz: configured writeable zone 'sub1.domain.tld' Jan 23 15:25:25 rtd-dc1 named[4942]: samba_dlz: configured writeable zone 'sub2.domain.tld' Jan 23 15:25:25 rtd-dc1 named[4942]: samba_dlz: configured writeable zone 'sub3.domain.tld' Jan 23 15:25:25 rtd-dc1 named[4942]: samba_dlz: configured writeable zone 'sub4.domain.tld' Jan 23 15:25:25 rtd-dc1 named[4942]: samba_dlz: configured writeable zone 'sub5.domain.tld' Jan 23 15:25:25 rtd-dc1 named[4942]: samba_dlz: configured writeable zone 'domain.tld' Jan 23 15:25:25 rtd-dc1 named[4942]: samba_dlz: configured writeable zone '_msdcs.main.domain.tld' Jan 23 15:25:25 rtd-dc1 named[4942]: set up managed keys zone for view _default, file 'managed-keys.bind' Jan 23 15:25:25 rtd-dc1 named[4942]: command channel listening on 127.0.0.1#953 Jan 23 15:25:25 rtd-dc1 named[4942]: managed-keys-zone: loaded serial 715 Jan 23 15:25:25 rtd-dc1 named[4942]: zone 0.in-addr.arpa/IN: loaded serial 1 Jan 23 15:25:25 rtd-dc1 named[4942]: zone 127.in-addr.arpa/IN: loaded serial 1 Jan 23 15:25:25 rtd-dc1 named[4942]: zone localhost/IN: loaded serial 2 Jan 23 15:25:25 rtd-dc1 named[4942]: zone 255.in-addr.arpa/IN: loaded serial 1 Jan 23 15:25:25 rtd-dc1 named[4942]: all zones loaded Jan 23 15:25:25 rtd-dc1 named[4942]: running Greetz, Louis> -----Oorspronkelijk bericht-----> Van: samba [mailto:samba-bounces at lists.samba.org] Namens Dirk Laurenz via> samba> Verzonden: maandag 23 januari 2017 14:58> Aan: samba at lists.samba.org> Onderwerp: Re: [Samba] DNS Update not working after update to 4.5.3>> Hi,>> i reduced to one reverse dns zone (192.168.x.x.) same error when> converting internal to bind_dlz>>> Jan 23 14:55:39 samba01 named[3279]: Loading 'AD DNS Zone' using driver> dlopen> Jan 23 14:55:40 samba01 named[3279]: samba_dlz: started for DN> DC=local,DC=laurenz,DC=ws> Jan 23 14:55:40 samba01 named[3279]: samba_dlz: starting configure> Jan 23 14:55:40 samba01 named[3279]: samba_dlz: configured writeable> zone '168.192.in-addr.arpa'> Jan 23 14:55:40 samba01 named[3279]: zone local.laurenz.ws/NONE: has no> NS records> Jan 23 14:55:40 samba01 named[3279]: samba_dlz: Failed to configure zone> 'local.laurenz.ws'> Jan 23 14:55:40 samba01 named[3279]: loading configuration: bad zone> Jan 23 14:55:40 samba01 named[3279]: exiting (due to fatal error)> Jan 23 14:55:40 samba01 systemd[1]: bind9.service: main process exited,> code=exited, status=1/FAILURE> Jan 23 14:55:40 samba01 rndc[3305]: rndc: connect failed: 127.0.0.1#953:> connection refused> Jan 23 14:55:40 samba01 systemd[1]: bind9.service: control process> exited, code=exited status=1> Jan 23 14:55:40 samba01 systemd[1]: Unit bind9.service entered failed> state.>>> that worked before...no bind complains about my forward lookup zone...?>> Am 23.01.2017 um 14:34 schrieb Dirk Laurenz via samba:> > hmm, just a guess:> >> > i have two reverse lookup zones:> >> > 192.168.2.x> >> > 192.168.6.x> >> > defined. should i define 192.168.x.x instead?> >> >> >> > Am 20.01.2017 um 15:21 schrieb L.P.H. van Belle via samba:> >> I suspect a zone overlap.> >> Did you add an extra zone manualy in bind?> >>> >> Or something like this... You added :> >> Zone1.Domain.TLD and then> >> Domain.TLD> >>> >> But then with the reverse zones.> >>> >> Because this :> >>> >>> Jan 20 13:58:09 samba02 named[10811]: zone 2.168.192.in-> addr.arpa/NONE:> >>> has no NS records> >> Does not look likes the samba_DLZ log lines but a pure bind log line.> >> Review you bind config and remove any manualy added zones.> >>> >>> >>> >> Greetz,> >>> >> Louis> >>> >>> >>> >>> >>> -----Oorspronkelijk bericht-----> >>> Van: samba [mailto:samba-bounces at lists.samba.org] Namens Dirk> >>> Laurenz via> >>> samba> >>> Verzonden: vrijdag 20 januari 2017 13:58> >>> Aan: Marc Muehlfeld; samba at lists.samba.org> >>> Onderwerp: Re: [Samba] DNS Update not working after update to 4.5.3> >>>> >>> Hi,> >>>> >>>> >>> i tried this hint and after restart of bind9:> >>>> >>>> >>> Jan 20 13:58:08 samba02 named[10811]: Loading 'AD DNS Zone' using> >>> driver> >>> dlopen> >>> Jan 20 13:58:09 samba02 named[10811]: samba_dlz: started for DN> >>> DC=local,DC=laurenz,DC=ws> >>> Jan 20 13:58:09 samba02 named[10811]: samba_dlz: starting configure> >>> Jan 20 13:58:09 samba02 named[10811]: zone 2.168.192.in-> addr.arpa/NONE:> >>> has no NS records> >>> Jan 20 13:58:09 samba02 named[10811]: samba_dlz: Failed to configure> >>> zone '2.168.192.in-addr.arpa'> >>> Jan 20 13:58:09 samba02 named[10811]: loading configuration: bad zone> >>>> >>> hmm bad luck... why got the PTR Zone lost....?> >>>> >>>> >>> Dirk> >>>> >>>> >>> Am 18.01.2017 um 18:03 schrieb Marc Muehlfeld:> >>>> Hi Dirk,> >>>>> >>>> Am 18.01.2017 um 08:51 schrieb Dirk Laurenz via samba:> >>>>> [2017/01/18 08:31:18.113146, 0]> >>>>> ../source4/dsdb/dns/dns_update.c:290(dnsupdate_nameupdate_done)> >>>>>> >>>>> ../source4/dsdb/dns/dns_update.c:290: Failed DNS update - with> >>>>> error> >>> code> >>>>> 110> >>>> Do you run the BIND9_DLZ or Internal_DNS back end?> >>>>> >>>> If it's BIND:> >>>>> >>>> https://wiki.samba.org/index.php/BIND9_DLZ_DNS_Back_End#Reconfiguring_the_> >>>> >>> BIND9_DLZ_Back_End> >>>>> >>>> Regards,> >>>> Marc> >>>> >>> --> >>> 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