search for: dsregdns

Hello Rowland, >> 3. I see the errors in the System log on the former DC (vm-dc1), like: >> The dynamic registration of the DNS record '_ldap._tcp.DomainDnsZones.domain.com. 600 IN SRV 0 100 389 vm-dc1.domain.com.' failed on the following DNS server: >> >> DNS server IP address: 172.26.1.83 >> Returned Response Code (RCODE): 0 >> Returned Status Code:

Hello, I've finally decided to switch all FSMO roles from Windows 2008 R2 DC (vm-dc1) to one of the two Samba 4.12.3 DCs (vm-dc3). Here are several issues I've faced after that: 1. After connecting DNS Manager to the all DCs, I've found that the SOA record for my domain and msdcs zones still point to the former PDC - vm-dc1. Is that OK? 2. So, I've changed the SOA manually

..."_msdcs.samdom.local" zone on SRVAD-OLD * set it to replicate forest-wide (some records should appear automatically) * set domain zone "samdom.local" and its reverse zone to replicate domain-wide * run these commands:     net stop netlogon     net start netlogon     nltest /dsregdns After these steps the join completed without issues at first shot. I've also reverted back to initial snapshots and retested the whole join again and I can confirm it works! Thanks to all the people that helped me solving the issue. Cheers Claudio

I've got the same problem. Have you ever found a solution to this trouble ? Regard, Ed

Il 05/03/2018 09:55, denis.shigapov via samba ha scritto: > Hi, run please to Windows DC command > dcdiag Already did it, both plain dcdiag and dcdiag /test:DNS. Nothing interesting in the output except for a warning at the end of /test:dns execution (Warning: Failed to delete the test record dcdiag-test-record in zone SAMDOM.LOCAL): ================= PS C:\Users\Administrator.SAMDOM>

On Sun, 4 Mar 2018 00:14:48 +0100 Claudio Nicora <claudio.nicora at gmail.com> wrote: > > > And I can now confirm that 4.7.4 on the latest Ubuntu 18.04 snapshot > > joins to a Samba AD domain as a DC. > I'm sure it does, that's why I suspect something is wrong in my > Win2000-->Win2008R2 upgraded domain AD. > > > Another thing that comes to my