samba - Jan 2016 - [samba4] DNS updates

Hai mathias, 

You welkom, always happy to help out and nice too hear you got it working. 

I must ask..  
Did you reboot the servers after you added the second server to the DNS?
And especialy in order, DC_with_FSMO, wait until its up again, then DC2. 
This often fixes the repliction problem and as far as i know, this only happend
just after the install of a extra DC.


Greetz, 

Louis

Hai Louis,

I should be able to answer you tomorrow: I pushed installation of 10 DC
before leaving work and this process would not be able to use workaround
described earlier because of SSH not yet open between the two sites. I
expect all other needed ports to be open, so I expect only the replication
workaround to be failed this night.
So tomorrow I should arrive at work with 10 DC joined to my AD and just
rebooted.
FSMO would not have been rebooted at that moment. If no replication took
place in the night I'll try to reboot FSMO then to reboot all DC one by one.

Greetings,

mathias

2016-01-20 16:39 GMT+01:00 L.P.H. van Belle <belle at bazuin.nl>:
> Hai mathias,
>
> You welkom, always happy to help out and nice too hear you got it working.
>
> I must ask..
> Did you reboot the servers after you added the second server to the DNS?
> And especialy in order, DC_with_FSMO, wait until its up again, then DC2.
> This often fixes the repliction problem and as far as i know, this only
> happend just after the install of a extra DC.
>
>
> Greetz,
>
> Louis
>
>
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>

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 replicate) from a replicated DC to all 10 new DC
and also force replication in the other way. All drs replicate commands
worked well.

Back to newly joined DC I launched samba_dnsupdate, on 10 DC this command
failed on 9 DC with mesage: "update failed: NOTAUTH". I rebooted all
joined
DC and samba_dnsupdate worked well on them.

This gave time to Samba to replicate things around and now all things goes
well.

Joining new DC is still a bit tricky in my opinion. Hoping this would work
better with 4.4.x

Cheers,

mathias


2016-01-27 19:33 GMT+01:00 mathias dufresne <infractory at gmail.com>:
> Hai Louis,
>
> I should be able to answer you tomorrow: I pushed installation of 10 DC
> before leaving work and this process would not be able to use workaround
> described earlier because of SSH not yet open between the two sites. I
> expect all other needed ports to be open, so I expect only the replication
> workaround to be failed this night.
> So tomorrow I should arrive at work with 10 DC joined to my AD and just
> rebooted.
> FSMO would not have been rebooted at that moment. If no replication took
> place in the night I'll try to reboot FSMO then to reboot all DC one by
one.
>
> Greetings,
>
> mathias
>
> 2016-01-20 16:39 GMT+01:00 L.P.H. van Belle <belle at bazuin.nl>:
>
>> Hai mathias,
>>
>> You welkom, always happy to help out and nice too hear you got it
working.
>>
>> I must ask..
>> Did you reboot the servers after you added the second server to the
DNS?
>> And especialy in order, DC_with_FSMO, wait until its up again, then
DC2.
>> This often fixes the repliction problem and as far as i know, this only
>> happend just after the install of a extra DC.
>>
>>
>> Greetz,
>>
>> Louis
>>
>>
>>
>>
>> --
>> To unsubscribe from this list go to the following URL and read the
>> instructions:  https://lists.samba.org/mailman/options/samba
>>
>
>