The Host-Based Virtual Host system works quite differently from
the Script-Based Virtual Host. It does not require any setup from
Web.Manager and each host is mapped easily to your "www" folder. It is also
much more powerful, providing ftp accounts, email aliases and pop
accounts. We have below, sample configuration forms for Host-Based
VirtualHosts. There are some disadvantages to Host-Based Virtual Hosts.
They don't support Frontpage, nor does it come with Webmanager and its suite
of tools.
WWW Server:
Your web-server has been mapped to a folder (directory) within your
main "www" folder. For example, if your Virtual Host is
"test.com",
a folder called "test.com" would be created and mapped to your "www"
folder. (i.e. www/test.com).
CGI-BIN:
A cgi-bin directory has been created in your VirtualHost's directory. To
install
CGI scripts, login via Web.Manager
(http://www.masterdomain.com/cgi-bin/Web.Manager/Web.Manager.cgi) of
your master server and install scripts into this directory.
FTP Server:
FTP accounts for each VirtualHost can be created via Web.Manager. Login via
Web.Manager of your master server, select "FTP Management", select create
account, enter the login, passwords and home directory and press enter to
create.
(Note: home directory:
e.g. /usr/home///htdocs/virtualhost.com>)
Email Server:
Incoming Mail Server (POP) : pop.virtualhost.com
Outgoing Mail Server (SMTP) : smtp.virtualhost.com
(replace "virtualhost.com" with appropriate domain name)
Email-Aliases
Email aliases can be created via Web.Manager. Login via Web.Manager of
your master server, select "Email Management" then Click on "Manage
Aliases"
after highlighting the appropriate VirtualHost.
Email-POP Accounts
Each VirtualHost shares the pop server of her master server. Meaning, any
pop user ids created would work for all its virtual domains. For example,
if you have created
a pop user id called "webvis", this pop user id will work across your
master domain
and any virtual hosts. All pop user ids therefore have to be unique.
What happens if "webvis" already exists as a pop user id for
masterdomain.com and
the VirtualHost requires a similar email-account as well? The solution is
simple, create
another pop account called "webvis-vhost", then map the alias
webvis@virtualhost.com to the pop account "webvis-vhost". This mapping
will allow you to create unique email
aliases at individual domains (e.g. sales@virtualhost1.com,
sales@virtualhost2.com) each mapped to their own individual POP account.
Changing Individual Email Passwords:
Individual pop mail users can change their passwords and manage other
aspects of their email
http://www.masterdomain.com/cgi-bin/Web.Manager/myemail.cgi
That's it!
ABOUT US
