Account Default
Choose the starting settings for newly created hosting accounts.
Where to find it: Root: Server > Configuration > Account Defaults. Reseller: Account Default in the server menu.
Available to: Root manages the full set of defaults. Resellers manage the shared IP and nameservers allowed within their delegated scope.
What this page does
Defaults establish a starting configuration. They do not replace packages, feature profiles, or existing per-domain overrides. PHP inheritance and web/cache inheritance are separate choices.
Before you start
Install the PHP runtime before choosing it. Cache and ModSecurity defaults only make sense when the corresponding services are available. Existing accounts are not bulk-updated by changing the new-account defaults.
Default options
| Option | Effect |
|---|---|
| Shared IP | Address used for new accounts when a dedicated address or other explicit selection does not override it. |
| Nameservers | Primary and secondary NS values, with optional third and fourth nameservers, for account creation. |
| Default PHP runtime and OPcache | Choose an installed runtime and whether new accounts begin with OPcache enabled. |
| PHP: apply to new addon domains and subdomains | Apply the configured PHP runtime and OPcache default when those child domains are created. |
| Enable ModSecurity for new accounts | Initial domain protection state when the module is available. |
| Enable Automatic Server Cache for new accounts | Initial server-cache activation. Per-domain settings remain in Cache Manager. |
| Web settings: apply to new addon domains and subdomains | Apply the web/cache account creation defaults to newly created child domains. |
| Dynamic and static cache TTL | Separate freshness periods. Supported values range from 1 minute to 30 days, for example 10m, 6h, or 30d. |
Updating existing DNS zones through the API
The nameserver API supports a separate, explicit update of existing managed zones. Supply the requested account or domain selection; use the all-existing-zones option only when a server-wide update is intended. Changing a default alone is not proof that previously created zones were rewritten. See the complete root/reseller API parameter reference.
How to use it
- Select the appropriate shared IP and nameservers and save that group.
- As root, select the installed PHP version, OPcache state, and child-domain behavior.
- Set the new-account web and cache defaults separately.
- Create or inspect an authorized test account or new child domain to verify the intended account creation result.
Result and next check
New resources receive the intended defaults; existing resources keep their saved settings unless an explicit apply/update operation was requested.
Theme color