It sounds like you have 1 website, and you want to make sure both public
users, and LAN users can see the content. I think it's best to do as Jason
suggested an use the public hostname as the CN, and do a subject alt DNS
name of the server.lan or you could create DNS records in your lan to
resolve
> -Original Message-
> From: MM
> Sent: Tuesday, December 23, 2014 8:30
>
> Hello,
>
> My network connectivity looks like:
>
> setting 1
> laptop -> corpfirewall -> ... -> homefirewall ->
> serverbox (httpd 2.4)
> in this setting, i have a public dns registered hostname
> autou
Hello,
My network connectivity looks like:
setting 1
laptop -> corpfirewall -> ... -> homefirewall -> serverbox (httpd
2.4)
in this setting, i have a public dns registered hostname autoupdated by my
ISP.
my homefirewall forwards all traffic https to serverbox.
setting 2
samelaptop -> sam
