Adding subdomain

Hello,

I have a main site http://domain.com (MVC 2 / ASP.Net 3.5), now I want to create a Subdomain underneath it http://subdomain.domain.com, which is still a MVC 2 application running in ASP.Net 4.0 with its own web.config, files, and etc. This is like having two applications in one directory but the other one is residing on a subdirectory.

But when I access http://subdomain.domain.com it will still point to the content of http://domain.com.

I have already tried to use the code for programmatically redirecting Subdomains to specific sub-directory. I have also purchased the "Unlimited Subdomain" add-on.

What am I still missing?

Can you please help me on this one out?

 

What's the downside of hosting multiple websites on the same domain?

This is not so much a question as a comment.

From this thread: http://community.discountasp.net/showthread.php?t=11971

I researched the issue of hosting multiple websites on the same domain.

Insofar as I can tell, there must be some downside to doing this, otherwise everybody would just have one domain and 1000 separate websites on it.

From what I can tell, the downsides are: 1) you don't get statistics reported for each of the 1000 separate websites, but the stats are all reported just for the one domain, 2) there is some sort of performance hit (not sure what though), 3) see below, multiple pointer records can cause an occasional bug somewhere.

Any other comments appreciated as to why this multiple hosting is not always optimal.

PJ2010

Multiple pointer records

While most rDNS entries only have one PTR record, DNS does not restrict the number. However, having multiple PTR records for the same IP address is generally not recommended, unless there is a specific need. For example, if a web server supports many virtual hosts, there may be one PTR record for each host and some versions of name server software will allocate this automatically. Multiple PTR records can cause problems, however, including triggering bugs in programs that only expect single PTR records and, in the case of a large web server, having hundreds of PTR records can cause the DNS packets to be much larger than normal.

 

The main drawback is all the sites on the account share the same application pool. So that means instead of one site having, for example, 200mb of memory available, that memory is shared by all the sites running on the account.

Additionally, any application pool-specific things like ASP.NET version, etc. have to be the same for all sites.