Replying here so that we can share progress (or problem) with other users:
We have performed some test with shahsx.
Here is the issue he faces. Perhaps some 3.2 users can comment and help.
Server is running file sharing service.
- trying to resolve Zentyal server name returns 2 IPs: one for the internal interface, one for the external interface
- if you remove Zentyal host in DNS using Zentyal GUI, then another entry is automatically (and quickly) added, visible in GUI but without any IP.
- if you add an IP, everything looks OK but after few minutes (about 8 minutes) although thre is no change at GUI level, another record is added to DNS, visible using
dig axfr [yourdomain]
and if you resolve this server name, you get 2 IPs again, one for the internal, one for the external.
My question here:
- aside the strange nslookup behaviour, may this prevent Windows users to authenticate against Zentyal DC ?
We could have pushed further tests, e.g. disabling file sharing service but I'm already pretty convinced that such wrong behaviour is due to Samba handling one part of DNS content management on the behalf of Zentyal administrator.
Someone to confirm or to explain what's wrong ?