| Author |
ssl AD Domain not External Domain
|
|
|
| I have a win2003 server with IIS that is on my active directory domain
(company.internal.com) and is accessible from the Internet by the domain name
(webserver.external.com). If I install an ssl certificate, will there be a
problem that the server is in a different domain (AD Domain) than the domain
name used to access the site from the Internet? The domain name I use to
access this server has nothing to do with the actual server configuration
with the exception of the IP Address it is pointing to.
| |
| Ken Schaefer 2006-09-28, 1:37 am |
| As long as you access the server using an FQDN that matches the "common
name" embedded in the certificate, there will be no problems. It does not
matter that the FQDN is different to the fully qualified AD DNS name that
the server has.
Cheers
Ken
"DB" <DB@discussions.microsoft.com> wrote in message
news:4B4AE6CF-84F7-4D6A-8D67-F5F5767EB1BA@microsoft.com...
>I have a win2003 server with IIS that is on my active directory domain
> (company.internal.com) and is accessible from the Internet by the domain
> name
> (webserver.external.com). If I install an ssl certificate, will there be a
> problem that the server is in a different domain (AD Domain) than the
> domain
> name used to access the site from the Internet? The domain name I use to
> access this server has nothing to do with the actual server configuration
> with the exception of the IP Address it is pointing to.
| |
|
| Thank you for the response.
"Ken Schaefer" wrote:
> As long as you access the server using an FQDN that matches the "common
> name" embedded in the certificate, there will be no problems. It does not
> matter that the FQDN is different to the fully qualified AD DNS name that
> the server has.
>
> Cheers
> Ken
>
> "DB" <DB@discussions.microsoft.com> wrote in message
> news:4B4AE6CF-84F7-4D6A-8D67-F5F5767EB1BA@microsoft.com...
>
>
>
|
|
|
|