My domain name is domain.com
Nethserver name is server.domain.com
AD server hostname is nsdc-server.domain.com
The certificate is valid for server.domain.com and nsdc-server.domain.com
Nethserver AD can use TLS, yes. This will use port 636.
Hi,
OK, is that correct?
I thougth, best practise is to use
My domain name is domain.com
Nethserver name is server.domain.com
AD server hostname is nsdc-server.**ad.**domain.com
THX
Thorsten
I have seen the NethServer installation procedure propose the exact same, but I really have no use for the AD on a subdomain. It overcomplicates the setup for no known-to-me reason. If it is best practice, I have missed a few things.
(It could probably be useful in a huge domain where you are not the single AD server in the domain (forest), like a departmental server)
Hello, @giacomo @mrmarkuz
hoping consider of the default certificate in the nethserver,I think give a user to choose his cert from web GUI be perfect 
Best Regards
I agree with you that would be cool, but still we didn’t find a simple solution which could work on all scenarios 
wrong directory (missing private directory)?
then what is the correct path?
/etc/pki/tls/private/localhost.key