Sorry for asking … mine is probably a stupid question, but since using 6.8 Enterprise version this was not necessary I’m curious to know if this is a specific feature of the enterprise or if is just a new way of working … also seems that aliases made using distribution groups in AD are not taken in NG 7. Can someone clarify ?
Thanks in advance.
ns7 was designed with less requirements against the domain account provider, to ease deploying it on different environments.
We cannot modify directly a LDAP entry in Active Directory, for instance the user’s mail address. For that reason we must keep the mail address in our database.
As a bonus, in ns7 the username is a valid email address itself. If the domain is a valid DNS domain it is ready to receive mail messages!
Right, but …also to read that field we need an authenticated client. We tried this solution on ns6, but ended up with a complex configuration I don’t want to maintain on ns7, too.
Absolutely agree, for AD those are the guidelines to follow!
However we don’t have such restrictions with OpenLDAP.
Because the DNS names of all the nodes that require name resolution include the Internet DNS domain name for the organization, choose an Internet DNS domain name that is short and easy to remember. Because DNS is hierarchical, DNS domain names grow when you add subdomains to your organization. Short domain names make the computer names easy to remember.
If the organization has an Internet presence, use names that are relative to the registered Internet DNS domain name. For example, if you have registered the Internet DNS domain name contoso.com, use a DNS domain name such as corp.contoso.com for the intranet domain name.come
For your Active Directory Domain Name, use a subdomain of your public domain.
