Virtual Subhosting is one of the most powerful features of the Virtual Private Server and the Apache Web Server. This feature allows you to support multiple domain names that each resolve to their own unique subdirectories on a single Virtual Private Server. In other words, you can host bob.com and jim.com on the same Virtual Private Server, each with its own domain name and unique site content. You can also offer each Virtual Subhost customer their own unique FTP login with access to their own subdirectory and E-Mail addresses using their own domain name.

When used correctly, Virtual Subhosting offers a powerful, value-oriented, and flexible platform.

Limitations of Virtual Subhosting

Virtual Subhosting is a great feature of our Virtual Private Server System. However, there are some limitations to this capability which you should understand. These limitation include the following:

1) Virtual Subhosting is made possible by the introduction of HTTP/1.1. In order to view subhosted domains you must have a browser which is HTTP/1.1 compliant. Generally speaking, Virtual Subhosting is supported by Netscape Navigator 2.0+, Mozilla FireFox, Safari, and MSIE 3.0+. Any other browser that is HTTP/1.1 compliant will be able to access a subhosted domain.

If you are using an older browser which is not HTTP/1.1 compliant you will not be able to view the sites, nor other sites which are using Virtual Subhosting. However, considering that together the web browsers referenced above, have 90-95% of the market share, this is generally not major a problem. Nonetheless, it is good to be familiar with this limitation.

2. A Virtual Private Server is capable of handling 30,000 to 50,000 hits (assuming hits generally request about 5 kb of data) per day. That is not visitors; the term hits refers to any request for a file (whether it's a .html, .gif, or any other type). If you have 5 Subhosted domain names, each which is trying to accommodate 10,000 hits per day (which really isn't that much if you have a graphically intensive page) there will likely be a problem. This slowdown will affect all of your clients on the Virtual Private Server you are using to Subhost. When a slowdown occurs a wise Reseller will properly manage his or her Virtual Private Server by reducing the number of Subhosts on the server by either upgrading one of the especially high traffic Virtually hosted sites to its own Virtual Private Server or by moving some Subhosts to a less busy server. Either way, proper load balancing is a science that a Reseller must understand in order to succeed with serious Virtual Subhosting.

3. A Virtual Private Server can only host a finite number of Virtual Subhosts due to performance reasons. Consider the following recommendations when deciding how many Subhosts to place on a single Virtual Private Server.

Server A - around 5 low volume subhosts

Server C - around 60 low volume subhosts

We cannot guarantee the number of Virtual Subhosts you will be able to host since each site uses a different amount of resources. It may be that you can only host one other Virtual Subhost before resources are exhausted on a Virtual Private Server. It is up to the customer to monitor Virtual Subhosts performance and instruct Gatman Services to upgrade high load Virtual Subhosts to their own platforms.

If a Subhost exhausts available resources it can be shut down with out notice. 

4) Virtual Subhosting obviously uses the resources of a single Virtual Private Server to accommodate the needs of multiple web sites. Among the resources that are shared is the single IP address that is associated with the Virtual Private Server. Search engine spiders which are not HTTP/1.1 compliant will not be able to index the sites. Most major spiders and search engines are now HTTP/1.1 compliant.

5) A Virtual Private Server can only support a single Digital Certificate. This can make the use of SSL difficult since all Subhosts must use the same Digital Certificate and only one domain name can be associated with a Digital Certificate.
6) A Virtual Subhost does not have telnet access to the Virtual Private Server.

7) There are some limitations to the E-Mail capability of Subhosts, namely how the Virtual Private Servers interpret E-Mail addresses. For instance, if you send an E-Mail to This e-mail address is being protected from spam bots, you need JavaScript enabled to view it and This e-mail address is being protected from spam bots, you need JavaScript enabled to view it , the server will view these as the same address. This is because SMTP programs (such as sendmail on the Virtual Private Server) do not differentiate between locally delivered domains. We have developed a way to get around this limitation by using a proprietary utility called virtmaps. VirtMaps require configuration, along with Alias, and POP account settings.

8) It is important to understand that giving cgi-bin access to your subhosted account is a potential security risk. This is because the CGIs have all of the rights and privileges of the CGIs the Virtual Host primary account may execute. Therefore, it is possible for a subhosted client, which has been granted CGI privileges, to read or remove any file in your directory hierarchy. Moreover, it is possible for a malicious Subhosted client to crack weak passwords and gain shell access to your Virtual Private Server.