Child pages
  • Tweak Settings - Domains
For cPanel & WHM version 70

Skip to end of metadata
Go to start of metadata

(WHM >> Home >> Server Configuration >> Tweak Settings)

Allow users to park subdomains of the server's hostname

This setting allows users to park subdomains on your server’s main domain.

For example, this setting impacts the example.com server with the following results:

  • If you select On, a cPanel user could successfully create the subdomain.example.com alias.
  • If you select Off, a cPanel user would receive an error message if they attempt to create the subdomain.example.com alias.

This setting defaults to Off.

Allow cPanel users to create subdomains across accounts

This setting allows a cPanel user to create an addon domain or subdomain of a domain that another cPanel user owns.

For example, if the user bob owns the domain example.com, the user charlie can create the store.example.com subdomain.

This setting defaults to Off.

Warning:

Do not enable this option. It can cause serious security issues.

Allow WHM users to create subdomains across accounts

This setting allows WHM users to create an addon domain or a subdomain of a domain that another user owns.

For example, if the user bob owns the domain example.com, the WHM user charlie can create an account for the store.example.com subdomain.

This setting defaults to Off.

Do not enable this option. It can cause serious security issues.

Allow Remote Domains

This setting allows users to create parked domains (aliases) and addon domains that resolve to other servers.

This setting defaults to Off.

Warning:

Do not enable this option. It can cause serious security issues.

Allow resellers to create accounts with subdomains of the server's hostname.

This setting allows resellers to create accounts with subdomains of your server’s main domain.

For example, if your main domain name is example.com, enable this setting to redirect user.example.com visitors to the reseller’s website.

This setting defaults to Off.

Allow unregistered domains

This setting allows users to create domain names on the server that they do not register with a valid registrar.

This setting defaults to Off.

Automatically add A entries for registered nameservers when creating a new zone

This setting specifies whether the system automatically creates A entries for a new domain's registered nameservers when a user creates a domain.

This setting defaults to On.

Replace SSL certificates that do not match the local hostname

This setting instructs the checkallsslcerts script to replace any SSL certificates that do not match the hostname of the server with a cPanel-signed certificate. This includes wildcard certificates.

This setting defaults to On.

Prevent cPanel users from creating specific domains

This setting prevents the creation of certain domains with domain names that the /var/cpanel/commondomains file contains.

If you enable this setting, cPanel users cannot create (as an addon or parked domain) any domain that the /var/cpanel/commondomains file or the /usr/local/cpanel/etc/commondomains file contains.

Important:

Do not edit the /usr/local/cpanel/etc/commondomains file directly. If you do, the system will overwrite your changes whenever cPanel & WHM updates.

Check zone syntax

This setting instructs the system to automatically check zone file syntax whenever a user saves or syncs DNS zone files.

This setting's value defaults to On.

Check zone owner

This setting instructs the system to automatically check a DNS zone’s owner whenever a user saves or syncs DNS zone files.

This setting defaults to On.

Enable DKIM on domains for newly created accounts

DomainKeys Identified Mai (DKIM) verifies a message's sender and integrity. It allows an email system to prove that a message is valid, not forged, and that it originated from the specified domain.

This setting allows you to specify whether to enable DKIM for new accounts by default.

This setting defaults to On.


Note:

The /scripts/enable_spf_dkim_globally script allows you to enable SPF and DKIM for existing accounts on the server, and create the appropriate DNS records for their domains. For more information, read our The SPF and DKIM Global Settings Script documentation.

Enable SPF on domains for newly created accounts

Sender Policy Framework (SPF) denies spammers the ability to send email when they forge your domain’s name as the sender (spoofing). This authentication function adds IP addresses to a list of computers that you authorize to send mail from your domain name. It verifies that messages that your domain sends come from the listed sender, which reduces the amount of backscatter that you receive.

This setting allows you to specify whether to enable SPF for new accounts by default.

This setting defaults to On.


Note:

The /scripts/enable_spf_dkim_globally script allows you to enable SPF and DKIM for existing accounts on the server, and create the appropriate DNS records for their domains. For more information, read our The SPF and DKIM Global Settings Script documentation.

DNS request management application

This setting specifies the application that the system uses to handle DNS management requests. 

To specify a new application, enter the path to the application that you wish to use in the text box.

This setting defaults to dnsadmin, auto-detect SSL.

Proxy subdomains

This setting allows users to access cPanel & WHM services from standard HTTP ports, such as Port 80 and Port 443. This setting proves useful if users cannot access the standard cPanel & WHM ports due to firewall restrictions.

If you enable this setting, the system automatically redirects visitors to the correct port when they access the following subdomains:

  • cpanel.example.com redirects to the user's cPanel Home Interface.
  • webmail.example.com redirects to the user's Webmail interface.
  • webdisk.example.com redirects to the user's Web Disk.
  • whm.example.com redirects to the user's WHM interface.

Note:

example.com represents the user's domain name.

This setting defaults to On.

Important:

  • The settings that you select in the Redirection tab do not apply to proxy subdomains.
  • When you enable this setting, it creates an entry in your Apache configuration file (httpd.conf). This feature also requires that you do not manually disable mod_rewrite and mod_proxy in the httpd.conf file.

Proxy subdomain creation

Proxy subdomains allow users to reach particular interfaces within cPanel or WHM when they enter a subdomain in a browser. For example, a user who enters cpanel.example.com reaches the example.com domains's cPanel Home Interface.

This setting allows WHM to automatically create DNS entries for the following subdomains for every user’s account:

  • cpanel.example.com
  • webmail.example.com
  • webdisk.example.com
  • whm.example.com

Note:

example.com represents the user's domain name.

This setting defaults to On.

Important:

  • You must add DNS entries for these subdomains to work. Use the /usr/local/cpanel/scripts/proxydomains file to create DNS entries manually.
  • WHM's Transfer Tool interface (WHM >> Home >> Transfers >> Transfer Toolignores this setting's value during an account transfer. If you set the Proxy Subdomains setting to On, the destination server will create proxy subdomains as if the account already exists.

Thunderbird and Outlook autodiscover and autoconfig support (enables proxy subdomain and SRV record creation)

This setting automatically creates autodiscover and autoconfig proxy subdomains when you create a domain.

  • autoconfig.example.com
  • autodiscover.example.com

This setting also creates theautodiscover and autoconfig SRV records that local domains need for Outlook and Thunderbird email autoconfiguation.

This setting defaults to Off.

Note:

If you turn off the Proxy subdomains option, the system disables this setting.

For more information about Autodiscover and AutoConfig, visit the TechNet for Autodiscover and Mozilla's AutoConfig websites. 

Preferred mail service to configure to use for Thunderbird and Outlook® autodiscover and autoconfig support

This setting allows you to choose the email transfer method to use with Thunderbird and Outlook with Autodiscover and AutoConfig support.

This setting defaults to imap.

Notes:

  • We recommend that you select IMAP and not POP3.
  • You must enable the Thunderbird and Outlook autodiscover and autoconfig support (enables proxy subdomain and SRV record creation) option in order to configure this setting.

Host to publish in the SRV records for Outlook autodiscover support.

Microsoft® Outlook®’s Autodiscover service searches DNS for an SRV record for an email inbox’s domain that points to a particular server for Autodiscover. By default, this server is cpanelemaildiscovery.cpanel.net.

This setting allows system administrators to perform the following actions:

  • Choose the host that the system publishes to the SRV records.
  • Change the default host if they have an SSL-enabled host with an SSL certificate that a Certificate Authority signs.
  • Use their own server for Outlook® Autodiscover. Enter that server’s Fully Qualified Domain Name (FQDN) in the available text box.
  • When you enable the Host to publish in the SRV records for Outlook autodiscover support feature, the system queries the server that you specify for the Autodiscover settings. You must have a custom XML file for this feature to function properly.

This setting defaults to cpanelemaildiscovery.cpanel.net.

Notes:

  • For more information about how to use a custom XML file, visit Mozilla's autoconfiguration page, or the Exchange's Autodiscover page.
  • You must enable the Thunderbird and Outlook autodiscover and autoconfig support (enables proxy subdomain and SRV record creation) option in order to configure this option.

For more information about Microsoft Outlook's Autodiscover feature, visit Microsoft's Support website.

Overwrite custom A records used for proxy subdomains

This setting allows the system to remove any existing custom A records that match proxy subdomains that you create or remove.

Notes:

This setting defaults to Off.

Overwrite custom SRV records used by Outlook AutoDiscover support

This setting allows the system to remove any existing custom SRV records whenever the user adds or removes Outlook Autodiscover support.

This setting defaults to Off.

Proxy subdomain override

This setting allows users to create cPanel, Webmail, Web Disk, and WHM subdomains that override automatically generated proxy subdomains.

For example, a user can direct visitors who access cpanel.example.com to a web page that the user configures, such as mycontrolpanel.example.com.

This setting defaults to On.

Notes:

  • Proxy subdomains allow you to enter a subdomain in your browser to reach particular cPanel & WHM interfaces. For example, enter cpanel.example.com to reach example.com's cPanel interface.
  • To enable this setting, you must disable the Overwrite custom A records used for proxy subdomains setting.

Restrict document roots to public_html

This setting prevents the creation of addon domains and subdomains outside of a cPanel user's primary domain's document root (the public_html directory within the user's /home directory).

For example, if you enable this setting and then create the example.com addon domain, the system creates the /home/username/public_html/example.com directory rather than the /home/username/example.com directory.

This setting defaults to On.

Use a Global DCV rewrite exclude instead of .htaccess modification (requires Apache 2.4 and EasyApache 4)

This setting allows Apache to use global mod_rewrite rules instead of .htaccess modification. These rules no longer require cPanel & WHM to modify each user's .htaccess file. 

EasyApache 4, with Apache 2.4, must be installed for this option to appear in the Tweak Settings interface. 

This setting defaults to Off.

You can enable the Global DVC Excludes setting through the Tweak Settings interface, or through the command line with the following command: 

whmapi1 set_tweaksetting key=global_dcv_rewrite_exclude value=1

Note:

When you enable this option, the system receives a trivial performance penalty because the HTTP requests must match against the DCV filename regular expressions.

Always use authoritative (registered) nameservers when creating a new DNS zone.

This setting allows the server to use a new domain's authoritative nameservers (the nameservers on record with the domain's registrar). The server does not use the nameservers that domain's creator specified.

This setting defaults to Off.

Additional documentation