Redirecting web site requests

  • Thread starter Thread starter Andrew Chalk
  • Start date Start date
A

Andrew Chalk

To IIS and network experts..

In order to update my application, I have set it up on two virtual
directories on the default web site on XP. For example, these are named APP1
and APP2. Then, I have set up a "main" site called APP. The APP site just
contains an entry under the "virtual directory" tab telling all requests to
be redirected to APP1 or APP2, depending which one is currently in
production. Ths poses a problem for people accessing the web site from an
internal LAN address. They use the internal lan address I.e.
http://192.168.0.2/APP but the redirection command in APP is specified with
the external address. For example http://66.138.76.169/APP1 or
http://66.138.76.169/APP2. The redirection doesn't work.

Is there anyway that I can redirect that will work from both internal and
external addresses?

Why can't an internal user access the site via the external address? I.e.
what is wrong with their routing?

Many thanks
 
Andrew said:
To IIS and network experts..

In order to update my application, I have set it up on two virtual
directories on the default web site on XP. For example, these are named APP1
and APP2. Then, I have set up a "main" site called APP. The APP site just
contains an entry under the "virtual directory" tab telling all requests to
be redirected to APP1 or APP2, depending which one is currently in
production. Ths poses a problem for people accessing the web site from an
internal LAN address. They use the internal lan address I.e.
http://192.168.0.2/APP but the redirection command in APP is specified with
the external address. For example http://66.138.76.169/APP1 or
http://66.138.76.169/APP2. The redirection doesn't work.

Is there anyway that I can redirect that will work from both internal and
external addresses?

Why can't an internal user access the site via the external address? I.e.
what is wrong with their routing?

Many thanks
Click to expand...
this is done in the setup of apache where I work
 
Users on the LAN will not be able to acceess the site using the
external address because they are probably behind a router running NAT.
This is a problem in your scenario. However you could purchase a domain
name and point it to your public IP. Then create a dns zone called
yourdomain.com on your internal DNS server. Create a record in that
zone to point to the private IP of the web server. Then both internal
and external users could access the site using the same address.

For example:
create an internal DNS Zone yourdomain.com
create an A record with the prefix www and point that to the internal
IP of the web server.

Your internal LAN users will resolve www.yourdomain.com as the private
IP of the webserver instead of your internal DNS server forwarding to
an external DNS server and providing the public address.
 
Many thanks, to Kurt and 'Smiles' as well. I am passing this on to the net
admin. to investigate.

Regards,

Andrew
 
I like Chris's answer the best. In fact to add to his idea, I believe you
can have multiple DNS entries for the same record, i.e.

65.10.200.201 www
192.168.0.201 www

and if netmask ordering is enabled and round-robin disabled (in a Windows
DNS server), you should always get the local address when accessing the
record form a computer with a local address.

....kurt
 
Back
Top