similar to: Missing DNS entry after "domain join"

Hi mathias, thanks for the heads-up! However, my AD Sites and Services is clear, too. I followed the suggestion here https://wiki.samba.org/index.php/Demote_a_Samba_AD_DC to use this http://gallery.technet.microsoft.com/scriptcenter/d31f091f-2642-4ede-9f97-0e1cc4d577f3#content script. Copy the contents of the "Visual Basic" box to a text file and rename it to

Am 29.10.2015 um 13:54 schrieb mathias dufresne: > Thank you for hint to this VBS script. In fact I alraedy saw it but I'm not > too confident in my VB knowledge, so I didn't use that script, prefering > rely on Samba command and shell scripts to work around issues. > > You spoke about SOA record which wasn't changed, same here. There is > another DNS record I had to

Am 29.10.2015 um 14:37 schrieb James: > On 10/29/2015 9:15 AM, Ole Traupe wrote: >> >> >> Am 29.10.2015 um 13:54 schrieb mathias dufresne: >>> Thank you for hint to this VBS script. In fact I alraedy saw it but >>> I'm not >>> too confident in my VB knowledge, so I didn't use that script, >>> prefering >>> rely on Samba

Am 30.10.2015 um 13:33 schrieb James: > On 10/29/2015 9:56 AM, Ole Traupe wrote: >> >> >> Am 29.10.2015 um 14:37 schrieb James: >>> On 10/29/2015 9:15 AM, Ole Traupe wrote: >>>> >>>> >>>> Am 29.10.2015 um 13:54 schrieb mathias dufresne: >>>>> Thank you for hint to this VBS script. In fact I alraedy saw it

Am 30.10.2015 um 14:56 schrieb James: > On 10/30/2015 9:19 AM, Ole Traupe wrote: >> >> >> Am 30.10.2015 um 13:33 schrieb James: >>> On 10/29/2015 9:56 AM, Ole Traupe wrote: >>>> >>>> >>>> Am 29.10.2015 um 14:37 schrieb James: >>>>> On 10/29/2015 9:15 AM, Ole Traupe wrote: >>>>>>

No replication this morning but FSMO was rebooted yesterday. Only joined DC were rebooted. After verifying all A records related to new DC were created, I forced creation of replication related DNS entries as described there : https://wiki.samba.org/index.php/Check_and_fix_DNS_entries_on_DC_joins#Resolve_the_objectGUID_CNAME_record_of_the_new_joined_Domain_Controller I forced replication (drs

Am 30.10.2015 um 15:20 schrieb James: > On 10/30/2015 10:11 AM, Ole Traupe wrote: >> >> >> Am 30.10.2015 um 14:56 schrieb James: >>> On 10/30/2015 9:19 AM, Ole Traupe wrote: >>>> >>>> >>>> Am 30.10.2015 um 13:33 schrieb James: >>>>> On 10/29/2015 9:56 AM, Ole Traupe wrote: >>>>>>

On 10/30/2015 10:11 AM, Ole Traupe wrote: > > > Am 30.10.2015 um 14:56 schrieb James: >> On 10/30/2015 9:19 AM, Ole Traupe wrote: >>> >>> >>> Am 30.10.2015 um 13:33 schrieb James: >>>> On 10/29/2015 9:56 AM, Ole Traupe wrote: >>>>> >>>>> >>>>> Am 29.10.2015 um 14:37 schrieb James:

Hi, I played with demote recently on a test AD domain composed with Samba version 4.3.0 and 4.3.1. I demoted all version 4.3.0. I was facing same issue as you. I written long mails here to explain how I managed that. My DNS looks clear now. Today I played with AD sites and I found in default sites all demoted DC. They weren't removed from DNS DB nor here. For now I have no idea how to get

On Sat, 20 Oct 2018 00:06:40 +0200 (CEST) tomict via samba <samba at lists.samba.org> wrote: > Thanks for the quick reply Rowland > > >Never ran an RODC (yet), but this all sounds like the problems that > >used to occur when joining a second DC, try reading this: > > >https://wiki.samba.org/index.php/Verifying_and_Creating_a_DC_DNS_Record > > > I

On 10/29/2015 9:15 AM, Ole Traupe wrote: > > > Am 29.10.2015 um 13:54 schrieb mathias dufresne: >> Thank you for hint to this VBS script. In fact I alraedy saw it but >> I'm not >> too confident in my VB knowledge, so I didn't use that script, prefering >> rely on Samba command and shell scripts to work around issues. >> >> You spoke about SOA

On 10/29/2015 9:56 AM, Ole Traupe wrote: > > > Am 29.10.2015 um 14:37 schrieb James: >> On 10/29/2015 9:15 AM, Ole Traupe wrote: >>> >>> >>> Am 29.10.2015 um 13:54 schrieb mathias dufresne: >>>> Thank you for hint to this VBS script. In fact I alraedy saw it but >>>> I'm not >>>> too confident in my VB knowledge, so

On 10/30/2015 9:19 AM, Ole Traupe wrote: > > > Am 30.10.2015 um 13:33 schrieb James: >> On 10/29/2015 9:56 AM, Ole Traupe wrote: >>> >>> >>> Am 29.10.2015 um 14:37 schrieb James: >>>> On 10/29/2015 9:15 AM, Ole Traupe wrote: >>>>> >>>>> >>>>> Am 29.10.2015 um 13:54 schrieb mathias dufresne:

Thank you for hint to this VBS script. In fact I alraedy saw it but I'm not too confident in my VB knowledge, so I didn't use that script, prefering rely on Samba command and shell scripts to work around issues. You spoke about SOA record which wasn't changed, same here. There is another DNS record I had to change: _ldap._tcp.pdc._msdcs.samba.domain.tld. I spoke about removing

Another question: 6° In DNS zone _msdcs, at root, there is one DNS record per DC. These records are those which have to create manually and are rlated to objectGuid as explained there: https://wiki.samba.org/index.php/Check_and_fix_DNS_entries_on_DC_joins#Resolve_the_objectGUID_CNAME_record_of_the_new_joined_Domain_Controller I have for now 4 DC in my second site, two of them have 2 records when

Thanks for the quick reply Rowland >Never ran an RODC (yet), but this all sounds like the problems that >used to occur when joining a second DC, try reading this: >https://wiki.samba.org/index.php/Verifying_and_Creating_a_DC_DNS_Record I Checked this, both the A record and the objectGUID CNAME records exist for DC1 and DC2 on bth servers. >You could try restarting Samba, there is

Ok, I made a backup following the Samba wiki and then did this. Had to wait a bit between updating the SOA's because I got a strange error message saying that a time value for the non-update of some resource cleanup wasn't set. But a few minutes later I could update the second SOA as well, and now the Samba log is clean. Ole Am 28.10.2015 um 16:42 schrieb Ole Traupe: > Hi, >

I ran thru the wikipage you linked to, and the results were as they should be # record 1 dn: CN=NTDS Settings,CN=DC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=tcsbasys,DC=com objectGUID: 0d5ebcac-88d7-44fb-a830-ec3eacb6757f # record 2 dn: CN=NTDS Settings,CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=tcsbasys,DC=com objectGUID:

On 10/02/16 11:20, mathias dufresne wrote: > Another question: > 6° In DNS zone _msdcs, at root, there is one DNS record per DC. These > records are those which have to create manually and are rlated to > objectGuid as explained there: > https://wiki.samba.org/index.php/Check_and_fix_DNS_entries_on_DC_joins#Resolve_the_objectGUID_CNAME_record_of_the_new_joined_Domain_Controller >

Hi, I demoted my PDC (DC1) forcefully, because replication (among others) wasn't working anymore due to hard disk failure and I was afraid of spending a lot of time on nothing. With DC1 offline I seized the FSMO roles on DC2 (4.2.5), restarted Samba, and found errors in the samba log due to the missing DC1. I removed the two DNS entries created according to this site: