Website assigned to internal IP and DNS

[docktek]

Hello,

Can someone help me understand how to make my website work from the WAN. For example, I've setup website

http://www.site1.com

on my server 2003 IIS 6 assigned to internal IP address 192.168.1.128. I've created a DNS entry on my local DNS to forward

http://www.site1.com

to 192.168.1.128.

I can type

http://www.site1.com

on my browser from LAN and works great.

How can I get this to work from the WAN?

I know if I change the IP address to "unassigned" on IIS, it works, but I need it assigned to an internal IP address because of SSL.

Any help in understand how to make this work would be greatly appreciated.

Thank You.

 

[58sniper]

Curious as to how an IP address is tied to SSL? SSL certificates have names (common and subject alternative) that are tied to DNS names.

Anywhere that the

http://www.site1.com

name is resolvable and a network path to the resolved IP exists, you should be able to get to it.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[docktek]

As you know the SSL is tied to the domain. In IIS you also define the domain when setting up a website. Supposely when the packet comes in from the WAN it matches the domain name and that's how the IP is resolved. Like I mentioned it works from my LAN, because of the DNS entry, I guess.

I think the problem with the WAN is a router issue. If I knew some way to make an entry in the router (cisco 892) to tell it to forward the packet to and internal IP, I guess it would work.