Forum Moderators: phranque
I know that.....
1) Each domain needs its own static IP address.
2) I point the A records of the domain to the new IP.
3) My router/firewall currently only allows 1 WAN IP. (209.)
4) Behind the firewall, I route port 80 requests to my webserver with one internal IP address (192.)
5) Various websites are set up with host headers on IIS.
6) Can't use host headers with SSL Certs.
7) Webserver only has 1 static Internal IP address.
8) Webserver still needs to be behind firewall.
What do I do and *how* do I do it?
Thanks.
However there may be a way if you running a DNS server on the machine itself?
Both items you mentioned are doable, but I can't figure out the last part - still having 1 server/box with multiple shared sites, but using IP addresses and not hostnames.
The IP address that appears in the dropdown box when I set up a new site is the static internal IP of the server itself.
I don't see a way, in IIS, to "install" new IP addresses for that machine.
It's in the TCP/IP configurations for the machine. Nothing to do with the webserver itself.
And I will need to get a better firewall/router. A friend recommended the Cisco pix 501.
That way I can have multiple externals, route them to individual internals, and have my SSL Certs.
I'll let you know if I get it all put together......
If you don't find the solution by the end of the week I will look into it in more detail.
My first Cisco...
My first Cisco...
Which one did you buy, tx? They're neat beasts. Give a shout if you have any issues setting it up. I used to do that in my former life. :)
I'm installing SSL Certs on my main sites and needed to learn how to deal with multiple IP addresses and my Linksys router/firewall just won't do that any more....
