« Previous Next »

• 10-14-2009, 11:58 PM

  Cosmopoet Joined on 10-26-2007, 12:44 AM Posts 66

  Network Web servers to two ISP's Reply Contact  Hello,  I hope I posted this in the right place :) I am currently hosting on IIS7 and have been since the product release. I have one ISP at the moment and I am looking to add another for redundancy. My question is I cannot seem to figure out how the IP mappings in the IIS manager for each site would be?   Example: If you had a site listening on 192.168.1.1 and you had this public IP that it was mapped to, go down from ISP #1, and the other ISP picked it up how would the mapping be set?  Would you run two host headers with different internal IP's with the same host name?   Better example: One Router with Load balancing: ISP #1 Public IP 1.2.3.4  NAT to 192.168.1.1 host header www.example.com ISP #2 Public IP 4.3.2.1  NAT to 192.168.1.2 host header www.example.com I think this is what I need to do just not sure? Any feedback would really put my mind at rest.  Thank you Joseph

• 10-18-2009, 3:22 AM

  In reply to

  stever@bitshop.com Joined on 04-19-2005, 1:15 AM Ashburn, VA Posts 13

  Re: Network Web servers to two ISP's Reply Contact The answer to this is VERY dependent on your network, and likely also your 2 ISPs. Generaly speaking to run 2 ISPs "properly" you need BGP Routing, in that case your IP configuration won't change - the same public IP will work.  The advantage of this is your web site will stay up. It sounds like you are describing 2 different IP subnets going to your web server - This technically will work fine, but it means your customers will need to realize www.example.com is down and use www-2.example.com (different public IP). Customers aren't goign to realize this though. Another option is to do this with multiple A records in DNS, but that's a bad solution too.  Yet another option is to run DNS servers on each conncetion, each answering with the public IP for that connection - however that's not pretty. You really need your public IP to stay the same and TRULY be multihomed. The only economical way to do this is to host somewhere professional that has multiple connections - Short of that it's not going to really do what you want cheaply. As to HOW: If you're just talking one site on the box just leave IIS bound to the default / all IPs (default setup) - Then on your NAT device forward to the IPs - i would put the server on 2 subnets, i.e. 192.168.1.2 and 192.168.2.2 - then use .1 of each subnet for the routers.  This way you can use IPs on either subnet for redundancy for outbound connections if you need to - i.e. some machines go on 192.168.1.* and 192.168.1.1 for default gw using connection #1, others use 192.168.2.* and 192.168.2.1 for default gw. Sorry this is long, it's NOT a good setup and that's the majority of my answer. There are some devices I believe that do this. Another option that's better is find a host that can forward this across a vpn to you - Why you'd want to do all this instead of just host the site I don't know but by using a vpn tunnel the host could have 2 paths.  I've questioned if there's a viable business model for doing that type of service for a long time but don't believe it is - The cost to sell/support it is too high from the hosts end and the cost savings would be trivial, if any at all, given virtualization reduced the cost for a cheap dedicated server.  Good luck,   Steve Radich - President BitShop.com - IIS Cloud Solution Coming Soon - Join our "Free 3 Month Beta" Waiting List Now...

• 10-18-2009, 11:27 AM

  In reply to

  Cosmopoet Joined on 10-26-2007, 12:44 AM Posts 66

  Re: Network Web servers to two ISP's Reply Contact Hello Steve,  First I would like to thank you for replying to my post. Also I do not mind at all that it is long. I would prefer that if it helps me out :) Go as long as you like...  A little more background is needed on me first. I am a hosting company of 12 servers and we are on one ISP now. Becasue of recent growth I have become a bit nervous at this setup as we started much smaller...2 servers . We are kinda happy about that. We have the MS SPLA's and all the gooddies - just this is not where I want the "weak link" to be. Up til' now we have had excellent service with our ISP and uptime has been great so has any repair turnaround time.( hope I don't jinx that here)  I have investigated the scenarios that you are talking about but not entirely the BGP option. However there are so many conflicting ways to do this.That led me here.Why? Because this is Windows and I am a Windows host. I was sure that someone kind enough to point me in the right direction would be here to help out. As for my network it is a Domain Network and it is on a single subnet on two routers.DNS and WINS for backup name resolution We cater to the smaller businesses and more of a private host than so much commercial like the bigger hosts. As for cost I am not sure as to what the cost would be for BGP? Were you referring to the router costs for BGP or the ISP intervention? Maybe both? Since there is more than one website, that negates the use the of the default setting in IIS. However after seeing this post I didn't realize that the same Public IP could be used in this situation. I was thinking more along the lines of a great CLI router that could handle this and Send one ISP in on the same subnet and the other in on the same subnet and use the DNS Option or Round Robin. But I totally agree with you on that method as I saw it as sloppy too. Not what I wanted to figure out if I had an issue. You post has sparked my interest in the BGP option and need to figure it out. Is there anyway that you could point me in that direction and maybe coach me out a little here? I want to sleep at night :)   Thanks again for your time. Joseph