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