PDA

View Full Version : Multiple sites on one server



Ian Telfer
8-Apr-2005, 03:37 AM
Hi All,

We're just setting up one server that will have multiple sites, each
with its own domain and external IP address.

What is the most efficient way of doing this, setting them up in IIS as
web sites each or using virtual directories within the default We Site?

WebApp Admin always creates sites as virtual directories under the IIS
default web site, but if you allocate all of the IPs to the default web
site, how does it know which virtual directory to point it to?

Thanks for any advice.

Cheers

Ian

Ian Telfer
8-Apr-2005, 04:20 AM
BTW, most will need to have their own Secure Cert, which I think means
that each needs to be in its own web site?

Ian

Ian Telfer wrote:
> Hi All,
>
> We're just setting up one server that will have multiple sites, each
> with its own domain and external IP address.
>
> What is the most efficient way of doing this, setting them up in IIS as
> web sites each or using virtual directories within the default We Site?
>
> WebApp Admin always creates sites as virtual directories under the IIS
> default web site, but if you allocate all of the IPs to the default web
> site, how does it know which virtual directory to point it to?
>
> Thanks for any advice.
>
> Cheers
>
> Ian

Knut Sparhell
8-Apr-2005, 04:48 AM
Ian Telfer wrote:

> We're just setting up one server that will have multiple sites, each
> with its own domain and external IP address.

Ok, but explicit IP-adresses for each site is not necessary for http,
only for multiple https sites usin the default https port.

> What is the most efficient way of doing this, setting them up in IIS as
> web sites each or using virtual directories within the default We Site?

Definately multiple web *sites*. They are separated *either* by their
unique IP address or their host name (containing the domain as
"www.mydomain.com"), or even by both (double checked).

> WebApp Admin always creates sites as virtual directories under the IIS
> default web site, but if you allocate all of the IPs to the default web
> site, how does it know which virtual directory to point it to?

You should not point all the IPs (or host names) to the default web
site, that is if the IPs are *dedicated* to a host name in diffrent
domains, in DNS. The default web site may and perhaps should be left
unused or used just for testing purposes or as a "trap". If you don't
have a special IP for the default site (probaly not), then use some
other host name or some special port, or just stop it.

When you create a web site, either specify an IP address (as you have)
or use the Advanced button to set up host names (or ports). Using ost
names is the common way to do this.

You may avoid Web Application Administrator creating a virtual directory
under the default web site by:

1. Selecting an *existing* virtual directory
2. Ignoring the warning message saying that it doesn't mathc the global.asa

or, better:

1. Delete the created virtual folder from the default web site, as this
is not needed an may be confusing.

2. Create a new web site for the application, with its root directory
pointing to the AppHtml folder of your application, and bound to the IP
address used in DNS for the host. You *may* also create virtual
folders, but you will probably not need any and you will probably want
to access the web app from the root. If not so, create a virtual folder
under the newly created site, and point it to the AppHtml folder.
------------------------------------------------------------------------

DNS, using separate IPs and A records:

www.site-a.com A 12.34.56.1
www.site-b.com A 12.34.56.2
www.site-c.com A 12.34.56.3

On server, bind each site to IP.

DNS, using a singe IP and CNAME records:

www.mywebserver.com A 12.34.56.1
www.site-a.com CNAME www.mywebserver.com
www.site-b.com CNAME www.mywebserver.com
www.site-c.com CNAME www.mywebserver.com

On server, let each site serve all IPs, bind each site to the host
names. This is what I would recommend it a typical situation. One IP
is easier to maintain, and have a lower cost than multiple IPs. In some
cases multiple IPs may be desirable in addition to using host names.


--
Knut Sparhell, Norway

Knut Sparhell
8-Apr-2005, 05:00 AM
Ian Telfer wrote:
> BTW, most will need to have their own Secure Cert, which I think means
> that each needs to be in its own web site?

I see. Then you will need your multiple IPs, at least as long all sites
will use the default https port 443. This is because https can't be
directed to a web site using the popular host name method, as the host
name remains undetectable inside the encrypted request package until
decrypted and processed at the actual web site.

In any case, https or plain http, when several applications is to be
accessed using different domain names, the only reasonable option is to
have multiple *sites*. Nothing to gain by not doing it other ways. No
reason to mess with other setups, and then forcing you to *redirect*
from the domain based host names to a virtual folder under another
domain than originally wanted.

--
Knut Sparhell, Norway

Ian Telfer
8-Apr-2005, 09:36 PM
Knut,

Thanks for the thought you give to your replies, its really appreciated.

Ian