I am running a production server with Samba4 AD and ofcourse DNS, but DHCP is not and will not be run on that server. I will likely use the firewall for that.
There is some confusion due to how the Samba container is used. Under AD rules, the AD server has to be DNS server as well. Not setting the IP of the Samba container as DNS for the clients, or using the DNS page on Nethserver to add DNS entries will yield loads of confusion.
When using Samba AD, do NOT use the DNS page on the Nethserver.
Instead, use Microsoft Management Console and it’s DNS snap-in to connect to the Samba container from a domain joined machine with an account that is member of the domain admins group, and you should be able to administer it as per normal.
We are a 15 people company, with below 100 customers, and we have all accounts in the AD, it works as full fletched AD replacement if you ask me, barring roaming profiles, but I swear to HHTFSM that I will get that to work…
ACL’s are posix, which sux a bit, but is doable for most practical purposes, and shares should be banned anyway … get Alfresco Share Community and have them versioned and better stored or see what any regular Owncloud installation can do for you. Shares should be a dying race, used only for specific purposes that need them for some odd reason, if you ask me.