Re: direct traffic to second webserver
- From: "Philip E." <groups@xxxxxxxxxxxxxxxx>
- Date: Mon, 2 Jun 2008 12:09:27 -0600
ISA would be able to route according to host header:
www.aaa.com = Server1
www.bbb.com = Server2
Does your firewall support this type of setup?
If not, then another alternative such as binding a second IP to the firewall (if possible) that is automatically forwarded to port 80 on Web Server 2 would work.
--
Philip E.
MPECS Inc.
Microsoft Small Business Specialists
http://blog.mpecsinc.ca
"yaz" <lesterhv@xxxxxxxxx> wrote in message news:6862b358-28ee-4818-a6ae-7071563c0891@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I'm struggling to set up a new domain on another webserver inside out
windows server domain.
We have two domains aaa.com and bbb.com
We have two servers server1 and server2
currently our firewall directs all incoming port 80 traffic to server
1 (which is our local DNS server). The nameserver routes both aaa.com
and bbb.com to the ip of the firewall, so both domains currently
resolve to the default IIS page on server1
How do I have bbb.com webpages served by server2?
Thanks to everyone for your help.
.
- Follow-Ups:
- Re: direct traffic to second webserver
- From: yaz
- Re: direct traffic to second webserver
- References:
- direct traffic to second webserver
- From: yaz
- direct traffic to second webserver
- Prev by Date: Re: direct traffic to second webserver
- Next by Date: Re: direct traffic to second webserver
- Previous by thread: Re: direct traffic to second webserver
- Next by thread: Re: direct traffic to second webserver
- Index(es):
Relevant Pages
|