I have a problem with naming the Active Directory domain of an internal server.
you have some options to name your AD domain:
The domain you use publicly (e.g. example.com)
This is not recommended because you get big problems (as Trump would say) with DNS.
But: apart from that it will work perfectly in NethServer.
The domain you use publicly with a not-existing TLD (e.g. exmaple.local or exmaple.internal, …)
This was the recommended proceeding years ago, but is not recommended anymore (see links above for details).
Problem in NethServer: every user is assigned the (totally useless) E-Mail address “firstname.lastname@example.org”. And there is no way known to me to deactivate this.
A subdomain of the domain you use publicly. (e.g. ad.example.com)
This is recommended by all publications I read.
But you got problems in NethServer:
- The NetBIOS name (which is automatically assigned) will be “AD” and can’t be renamed (as far as I know).
- Every user is assigned the (also totally useless, see above) E-Mail address "email@example.com". And this can’t be deactivated.
So how to proceed?
Is there a chance to use the “mail” field of the AD user as the E-Mail address instead of the login with AD domain name as suffix? So option 2 und 3 may be considered?
And is there a chance to rename the NetBIOS domain in option 3?
If this can’t be done, I think I would go on with option 1 and try to go round the DNS problems…