search for: samba_dn

Hi, I recently noticed that when doing "samba_dns --all-names --verbose" against Bind-9.12, I can't update dns records. I'm getting these error messages for each record to update: . . . update failed: REFUSED Failed nsupdate: 2 update(nsupdate): SRV _ldap._tcp.Default-First-Site-Name._sites.ForestDnsZones.samdom.com alpine.samdom.co...

...manually added SRV records, we are able to DCPROMO but then DNS( and it turns out AD replication) issues. The AD replication issues is due to DNS not replication and not copying the _msdsc_ zone file. So what is the best option in our case? Domain Prep/Migrate using BIND9_DLZ and the stick to the SAMBA_DNS? One question is would it help if we add the SRV records to the /var/cache/bind/zone file pre migration? Will the migration read that file and convert it to the DNS DB? Thank you. Regards, Praveen -----Original Message----- From: Andrew Bartlett [mailto:abartlet at samba.org] Sent: Tuesda...

On 28/08/2019 14:18, L.P.H. van Belle via samba wrote: > I think his question was. > > Is there a way to convert flatfile to samba-AD dns. > As far i know, not, but that should be pretty easy to script. > If that is the case, then it should be easy to script the transfer of records, but I do not think that was what the OP asked about ;-) Rowland

On Fri, 14 Oct 2016 15:16:17 +0200 Ronny Forberger via samba <samba at lists.samba.org> wrote: > > > Am 14.10.2016 um 15:05 schrieb L.P.H. van Belle via samba: > > Hai, > > > > Can you download : > > http://downloads.van-belle.nl/samba4/samba-check-db-repl.sh > > > Hi, > > the output of your script is > > No Samba DC's Found

> Nobody has looked into it yet. Likely just an extra build rule > required, I would need to see the 9.11 and 9.12 DLZ header files to > check. > > Aaron Haslett (CC'ed) may be able to help once he fights past the other > BIND9 issues he is looking at. > > Andrew Bartlett Thanks for response. I actually looked it myself. Since there is no DLZ ABI changes since

Hi, We migrated from Samba 3 to 4 (4.6.7-Ubuntu) and added promoted a Server 2008R2 as a Domain Controller. We've come across the following issues and request some suggestions to resolve them - The migration didn't generate DNS entries for the new realm. We had to manually create a new zone file (/var/cache/bind) for the new realm. Only then we were able to promote the