om: Steve Kradel [mailto:skra...@zetetic.net]
> Sent: Monday, December 10, 2012 11:48 AM
> To: NT System Admin Issues
> Subject: Re: SSL and the new no internal names ruling
>
> Well, this is certainly a terrible article from Digicert. Rename or
> migrate your domain in order to get c
Thanks for your work to clear things up, good job.
-Original Message-
From: Brian Desmond [mailto:br...@briandesmond.com]
Sent: Tuesday, December 18, 2012 6:41 PM
To: NT System Admin Issues
Subject: RE: SSL and the new no internal names ruling
Just to close the loop on this, thanks to
t: Re: SSL and the new no internal names ruling
Well, this is certainly a terrible article from Digicert. Rename or migrate
your domain in order to get certs that match your AD FQDN?
Links to ADMT?? Utter madness. Just use an internal CA for an intranet site,
as nobody else will be able to re
HAHAHAHAHAHA.
So did I. :)
-Original Message-
From: Brian Desmond [mailto:br...@briandesmond.com]
Sent: Monday, December 10, 2012 1:00 PM
To: NT System Admin Issues
Subject: RE: SSL and the new no internal names ruling
I reached out to DigiCert about this.
Thanks,
Brian Desmond
br
I reached out to DigiCert about this.
Thanks,
Brian Desmond
br...@briandesmond.com
w - 312.625.1438 | c - 312.731.3132
-Original Message-
From: Steve Kradel [mailto:skra...@zetetic.net]
Sent: Monday, December 10, 2012 11:48 AM
To: NT System Admin Issues
Subject: Re: SSL and the new no
Well, this is certainly a terrible article from Digicert. Rename or
migrate your domain in order to get certs that match your AD FQDN?
Links to ADMT?? Utter madness. Just use an internal CA for an
intranet site, as nobody else will be able to resolve those names
anyhow. Buy certs from a public
I thought the way to do it for Exchange was to use split brain DNS so you use
the same external domain name but pointing to internal IP's when internal?
From: Rick Berry [mailto:rbe...@elevativenetworks.com]
Sent: 10 December 2012 15:13
To: NT System Admin Issues
Subject: SSL and the new no inter
