robb
October 17, 2019, 4:44pm
77
@NLS I agree Samba4 AD provider installed directly in NS is preferable. Unfortunately CentOS 7 does not provide Samba4 packages and that is the reason why we need another solution.
[quote=“salvois, post:12, topic:4865, full:true”]
As a side note, I still don’t get why Samba has to be run in a container. [/quote]
I fully share. I’m discovering Nethserver I can’t yet figure out why such constraint, design choice or whatever reason behind this.
However I’m very far from having read lot of documentation or forum yet.
Nevertheless, it looks very strange too me
What is the exact relationship between the NethServer install and the nsdc? Is the nsdc a container? VM? Docker image? When pointing to a Domain Controller should I be asking for AD DC services from the NethServer IP or the nsdc?
I assume the DNSMasq DNS running on NethServer should essentially be ignored when using the nsdc. Correct?
Also: What DNS solution is the nsdc using? BIND9? If so: is the nsdc’s bind instance using the DLZ module?
Thanks!
And recently it became clear CentOS 8 will not ship Samba4 packages either
I installed a RHEL 8 beta to grab an impression of what is coming up from the next major version and I didn’t find a samba-dc packge. After a little search I found this article:
https://access.redhat.com/solutions/3705031
In short it says Red Hat will not provide such package in the future because AD is complex to deploy and to support. They could reconsider their decision if the market conditions will change.
That sounds a bit scary and I’m eager to listen other opinions/experiences about
r…
2 Likes