it doesn't matter, problem is with both backends... 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 >
On Fri, 20 Jan 2017 13:55:44 +0100 Dirk Laurenz via samba <samba at lists.samba.org> wrote:> it doesn't matter, problem is with both backends... > >As it works for me with 4.5.3, can you post your smb.conf Rowland
yes - sure - currently samba dns backend... # Global parameters [global] netbios name = SAMBA01 realm = LOCAL.LAURENZ.WS workgroup = LAURENZ server role = active directory domain controller dns forwarder = 8.8.8.8 allow dns updates = nonsecure idmap_ldb:use rfc2307 = yes client ldap sasl wrapping = sign # server services = -dns [netlogon] path = /var/lib/samba/sysvol/local.laurenz.ws/scripts read only = No [sysvol] path = /var/lib/samba/sysvol read only = No Am 20.01.2017 um 14:24 schrieb Rowland Penny via samba:> On Fri, 20 Jan 2017 13:55:44 +0100 > Dirk Laurenz via samba <samba at lists.samba.org> wrote: > >> it doesn't matter, problem is with both backends... >> >> > As it works for me with 4.5.3, can you post your smb.conf > > Rowland >