2 sites (1 http, 1 https), 1 server.

[sorehead]

Hi,

IIS6/Windows 2003.

At the moment I have 1 site running through http fine, over a top end port number to make the address

http://www1.mydomain.com:60606.

This works fine both internally and externally. My ISP handles DNS and entered

http://www1.mydomain.com

to resolve to 213.x.x.53. All good, I don't want to change it.

On the same server I have another site running internally on port 80, but I want to implement ssl on this and make it accessible externally. So, the questions:

1) Can my ISP assign 2 dns names to the one external IP? So make site.mydomain.com resolve to 213.x.x.53 as well? I can't see why not.

2) Can I then get a cert for site.mydomain.com, install it and then tick the ssl box and have it work? Or will ssl not like the same (external) ip address resolving to 2 different names. Is there a problem with reverse dns resolution?

I have NAT in operation.

I read that I can give the server and therefore the sites different internal IP's. Would this help? Or maybe host headers? (whatever they are...)

I'm learning IIS so any help you give would be gratefully received.

Thanks

Jim..

 

[mrdenny]

1) Yes, no problem.
2) Yes that will work fine. There's no problem with reverse dns. It's not used for SSL.

Host headers won't help, as the host header is encrypted within the SSL encrypted http request so you can't use host headers with SSL. Just setup a second web site in IIS having it listen on port 443 with the cert, and you should be all set.

Denny

--Anything is possible. All it takes is a little research. (Me)

 

[sorehead]

That's great, thank you very much.

Jim

 

[mrdenny]

no problem.

Denny

--Anything is possible. All it takes is a little research. (Me)