I am working on a domain on a strictly internal LAN created a SA named with a .local suffix. I am just now learning about how .local domains are problematic now. http://www.mirazon.com/so-you-have-a-local-domain-now-what/ I am trying to get Portal for ArcGIS running on my server on this domain. This system requires https to communicate with clients and its layers. http://enterprise.arcgis.com/en/portal/10.3/administer/windows/enable-https-on-your-web-server-portal-.htm# My SA launched a local Certificate authority, created a certificate for me named server.dommainname.local, and I thought I got it working on the local IIS and bound it to port 443. However, client connections from browsers still report security problems. The cert is not recognized. Is this because the local domain is named *.local?
I talked to GoDaddy about buying a cert from them, but they told me their certs will not work on a .local domain. They said domains like this are not longer “fully functional domain names”. But will this also not work if we generate a domain cert from our local authority?