π Plan Template configuration
In EdgeHit CDN, User Plans are applied to user accounts to allow users to create their own DNS Domain Zones or define CDN Domains. For reference, see:
Plan templates act as predefined configuration sets that simplify the creation of consistent user plans. Instead of manually entering settings for each user, admins can apply a pre-configured plan template, ensuring standardization and reducing setup time.
In this section, we will discuss about the CDN Plan and DNS Plan settings. Plan templates can be managed under the following sections:
Home > DNS > PlanHome > CDN > Plan
Note
The settings described below can also be customized when creating a new User Plan. Using a pre-configured plan template is highly recommended when provisioning similar plans for multiple users, as each user requires an independent copy of the plan.
π DNS Plan Settings
DNS Plans that can be applied to user accounts. These templates simplify the provisioning of DNS capabilities by setting boundaries and defaults on a per-user basis.
βοΈ General Settings
These define the base limits and resource quotas associated with a userβs DNS usage.
| Field | Description |
|---|---|
| TTL Min Value (Unit: Seconds) | The minimum allowed TTL (Time to Live) value for any DNS record created under this plan. |
| TTL Max Value (Unit: Seconds) | The maximum allowed TTL value for records. |
| TTL Default Value (Unit: Seconds) | The default TTL applied when the user doesnβt explicitly set a TTL for their DNS record. |
| Max Number of Domains | Limits how many domain zones a user under this plan can create. |
| Max DNS Records per Domain | Restricts the total number of DNS records (A, CNAME, etc.) a single domain can contain. |
| Max Number of A-type Records Pointing to IPs | Limits the number of A records allowed. Helps prevent abuse or over-configuration. |
| Description | Optional text to describe the plan's purpose. |
π CDN Plan Settings
CDN Plan templates in EdgeHit define how CDN features and limitations are applied to user accounts. These plans help standardize performance, access, and security parameters across users.
βοΈ General Settings
These define the base limits and resource quotas associated with a userβs CDN usage.
| Field | Description |
|---|---|
| Package Traffic (Unit: MB) | The amount of CDN traffic included in the plan before overage charges apply. |
| Excess Rate (USD/GB) | The charge per GB of traffic when usage exceeds the planβs traffic quota. |
| Max number of domains | Limits how many CDN-enabled domains a user can create. |
| Max number of cache rules | Restricts the number of cache control rules that can be defined. |
| Max number of cache purges per day | Maximum number of cache purge requests allowed in a 24-hour period. |
| Max number of cache prefetches per day | Limits how many prefetch requests can be made daily. |
| Max number of WAF firewall rules | Caps the number of Web Application Firewall (WAF) security rules. |
| Max number of WAF rate limit rules | Restricts the number of WAF-based rate limiting rules. |
| WAF rate limit max statistical duration (Unit: Seconds) | Time window used to evaluate traffic rates. |
| Max duration of WAF rate limiting action (Unit: Seconds) | Duration for which a client is blocked or limited when a WAF rule is triggered. |
𧩠Plan Feature Options
These toggles and settings allow you to enable or restrict access to advanced CDN features.
| Field | Description |
|---|---|
| WebSocket | Enables support for WebSocket connections through the CDN. |
| Max number of WebSocket connections | Limits concurrent WebSocket connections per user/domain. |
| Client max upload limit (Unit: MB) | Restricts maximum file upload size per request. |
| Enable auto SSL cert | Automatically issues SSL certificates via Letβs Encrypt for user domains. |
| Custom origin server port | Allows users to define non-standard origin ports. |
| Custom origin server host header | Lets users set custom Host headers when contacting their origin. |
| Max number of origin servers | Maximum number of origin IPs/hosts that can be defined for one domain. |
π©Ί Origin Routing Policy & HealthCheck
These settings govern how CDN routes traffic to origin servers and how it handles failures or outages.
| Field | Description |
|---|---|
| Load Balancing | Configure available options for Load balancing Options in CDN Domain. |
| Fail timeout max/min/default value (Unit: Seconds) | Controls the interval between retry attempts when an origin is marked as failed. |
| Max number of fails | The maximum number of consecutive failures before the origin is marked unhealthy. |
| Min number of fails | Minimum threshold of failures before triggering a failover. |
| Default number of fails | Default value used for failure threshold unless overridden at domain level. |
By configuring these settings through a plan template, administrators can enforce consistent policies and performance boundaries across all user accounts.