If you are going to serve numerous users with a
great number of domains, you may want to create hosting configuration
presets, referred to as domain templates, which will simplify setting
up hosting accounts for new domains and web sites.
The templates cover
all resource usage allotments, permissions and limits that you can
define for a hosting account, plus mail bounce and Web statistics
retention settings.
Template name.
Specify a name for this template.
Mail to nonexistent users.
Specify the domain-wide mail bounce options
WebMail.
Specify whether the users of mailboxes in this domain should be able to
read their mail through a browser based WebMail
application.
Maximum number of subdomains. Specify the number of subdomains that can be hosted under this domain.
Maximum number of domain aliases.
Specify the total number of additional alternative domain names that
the site owner will be able to use for his or her web site.
Disk space.
Specify the total amount of disk space allocated to a hosting account
associated with the domain.
Maximum amount of traffic.
Specify the amount of data in megabytes that can be transferred from
the web site during a month.
Maximum number of web users.
Specify the number of personal web pages that the domain owner can host
for other users under his or her domain.
Maximum number of databases. Specify the number of databases that can be hosted in a domain.
Maximum number of mailboxes. Specify the number of mailboxes that can be hosted in a domain.
Mailbox quota.
Specify the amount of disk space in kilobytes that is allocated for
storing e-mail messages and autoresponder attachment files to each
mailbox in a domain.
Maximum number of mail forwarders. Specify the number of mail forwarders that can be used in a domain.
Maximum number of mail autoresponders. Specify the number of automatic responses that can be set up in a domain.
Maximum number of mailing lists.
Specify the number of mailing lists that the domain owner can run in a
domain.
Maximum number of Java applications. Specify the maximum number of Java applications or applets that the domain owner can install under a domain.
Validity period.
Specify the term for a hosting account.
Log rotation.
All connections to the Web server and requests for files that were not
found on the server are registered in log files. These log files are
analyzed by the statistical utilities running on the server, which then
present graphical reports on demand. If you need to view the contents
of these raw log files for debugging purposes, on your Home page, click
the domain name you need, click
Log Manager,
and then click the log file name you need. To prevent these log files
from growing too large, you should enable automatic cleanup and
recycling of log files:
- select the Switch on log rotation checkbox
- specify when to recycle log files
- specify how many instances of each log file processed by Plesk's statistical utilities to store on the server
- specify whether they should be compressed
- specify whether they should be sent to an e-mail address after processing.
Web and traffic statistics retention. Specify the number of months during which the Web and bandwidth usage statistics should be kept on the server.
DNS.
Specify whether the DNS server on your Web host should act as a master
(primary) or slave (secondary) name server for the domain name zone.
Physical hosting account. If you are going to host not only domain names, but also web sites, select the
Physical hosting checkbox and specify:
- Hard disk quota.
In addition to the soft quota, you can specify the so-called hard quota
that will not allow writing more files to the web space when the limit
is reached.
- SSL support.
To allow SSL
encryption for Web sites, select the SSL support check box.
- Create and publish site using Sitebuilder. This will enable the domain administrator to create and manage a Web site using Sitebuilder.
- Use a single directory for housing SSL and non-SSL content.
By default, when users publish their sites through their FTP accounts,
they need to upload the Web content that should be accessible via
secure connections to the
httpsdocs directory, and the content that should be accessible via plain HTTP, to the httpdocs directory. For the convenience of publishing all content through a single location – httpdocs directory, select the Use a single directory for housing SSL and non-SSL content check box. - FrontPage support.
To enable
users to publish and modify their sites through Microsoft FrontPage,
select the FrontPage support and FrontPage over SSL supportFrontPage authoring option to allowed.
- Support for programming and scripting languages widely used in development of dynamic Web sites and server-side Web applications.
Specify which of the listed programming and scripting languages
should be interpreted, executed or otherwise processed by the web
server.
- Web statistics.
- Custom error documents.
If you wish to create your own error pages and
use them on your server or allow your customers to do that, select the Custom error documents checkbox.