Best laid plans go awry... Our AD domain is us.domain.com but management now wants to use domain.com for all URLS (e.g. Intranet, My Site, ReportServer). Internal DNS is all set up for the domain.com zone (which happens also to be our external DNS domain
name) because we already use domain.com internally for some other servers.
We will be using Kerberos. My understanding is that Kerberos requires the real fqdn of computer based on domain membership. Should we just set up our host headers and Kerberos SPNs normally using the us.domain.com fqdn and then use AAM for the domain.com
View Complete Post