Additional domain controller failed if the primary domain controller changes the IP address

[Sulecio]

Describe the bug
Additional domain controller failed if the main server ip changes, if it allows to change the ip address but does not show the field to update the password, and does not allow to start services giving a connection error with the owner of the scheme

I have changed the ip of the main domain controller, but in a zentyal 7.0 that is as an additional controller, it allows updating the ip but it does not connect giving a schema error, nor does it allow updating the key to try to join it again

[djoven89]

Hi @Sulecio ,

I need more details to understand and replicate the bug in a lab. Could you please provide me with all the details you can? For example:

• Are both domain controllers use Zentyal 7.0?
• Was this ADC working correctly until the IP of the DC01 changed?
• When you found out that the ADC was not synced correctly, you made some changes in this form, is this correct?

What debugging actions did you do? Did you analyze any of the following?

• Log files:
  • /var/log/zentyal/zentyal.log
  • /var/log/syslog
  • /var/log/samba/samba.log
• DNS entries that have the DNS-DC as this another link explains.
• Replication status as this link describes.
• Did you see if the IP was correctly applied to DC01? Sometimes, the Domain Controller module still listens in the old IP.

Best regards, Daniel Joven.

[Neustradamus]

@Sulecio: Any news on this ticket?