search for: bin9_dlz

Hi, >What i hoped it to try to "upgrade" you internal DNS to bind9_dlz >And with doing that, avoid this bug. My production DCs use DNS Internal, so can I join a new DC using Bin9_dlz without problems? Regards, M?rcio Bacci Em qua, 28 de ago de 2019 ?s 12:14, L.P.H. van Belle via samba < samba at lists.samba.org> escreveu: > Hai Marcio, > > > ________________________________ > > Van: Marcio Demetrio Bacci [mailto:marciobacci at gmail.com] >...

...se ... just some CNAME records to enable that the browser can sparate credentials for different services running on same hosts. I am neither an expert in DNS/DHCP nor do I know anything about kerberos or ldap :( - just the ordinary lazy "never change" guy ;). I started playing using BIN9_DLZ dns backend. After having everything in place I recognized that the module does not update the records in existing zones as expected. Instead it took the control of the complete zone itself and allows no other GODs (my db.* files for that zone): ---cut--- named[3013]: samba_dlz: started for DN DC=...

...e 2019 ?s 13:17, Marcio Demetrio Bacci < marciobacci at gmail.com> escreveu: > Hi, > > >What i hoped it to try to "upgrade" you internal DNS to bind9_dlz > >And with doing that, avoid this bug. > My production DCs use DNS Internal, so can I join a new DC using Bin9_dlz > without problems? > > Regards, > > M?rcio Bacci > > Em qua, 28 de ago de 2019 ?s 12:14, L.P.H. van Belle via samba < > samba at lists.samba.org> escreveu: > >> Hai Marcio, >> >> >> ________________________________ >> >>...

Hai, I re-checked your config that looks all good, few minor things. Now, i noticed this in Andrews comment. Quote: The problem here is that Samba's python libraries are trying to find the DNS record they just added over RPC, but can't using LDAP. They do this to fix the ownership of the records, as otherwise they will be owed by the administrator, not the DC. What is in