DCV Policy

A DCV Policy ties a Provider and a Provisioner together and defines the automation rules for domain control validation. It answers: which domains to validate, when to run, and how to handle retries and timeouts.

A Policy is the only DCV object that is executed, it drives the full validation workflow using its Provider and Provisioner.

How to configure a DCV Policy

1. Log in to Horizon Administration Interface.

2. Access DCV Policies from the drawer or card: DCV  Policies.

3. Click on Add Policy.

4. Fill in the mandatory fields.

General

  • Name* (string input):
    Enter a meaningful policy name. It must be unique for each DCV policy. Horizon uses the name to identify the policy.

  • Provider* (select):
    Select the DCV Provider (CA connection) to use for this policy.

  • Provisioner* (select):
    Select the DCV Provisioner (DNS connection) to use for this policy.

Schedule

  • Schedule* (cron expression):
    Define when the policy runs automatically. The policy can also be triggered manually via the API at any time.

  • Renewal window* (finite duration):
    How far in advance of domain expiration Horizon triggers revalidation. Only domains expiring within this window are selected for the current run.

Filters

  • Domain filter (regex):
    Optional regex to restrict which domains this policy manages. Only domains whose name matches this pattern are selected for validation. Leave empty to process all domains returned by the Provider.

Retry and Timeout

  • Retry delay* (finite duration):
    Time Horizon waits before retrying a failed validation step. Horizon resumes from the failing step, not from the beginning of the pipeline.

  • Execution timeout* (finite duration):
    Maximum duration of a single policy run. When exceeded, the run is terminated and any unfinished domains will be retried on the next scheduled execution.

Triggers

Triggers are lifecycle hooks fired at key points during a policy run. Each trigger field accepts one or more existing Email, Groupware, or REST notifications to call when the corresponding event occurs.

  • On DCV Policy Start (multiselect):
    Select notification(s) to call when a policy run begins.

  • On DCV Policy End (multiselect):
    Select notification(s) to call when a policy run completes (all domains reached a final state).

  • On DCV Validation Success (multiselect):
    Select notification(s) to call when a domain is validated successfully.

  • On DCV Validation Failure (multiselect):
    Select notification(s) to call when a domain reaches an unrecoverable error state.

  • On DCV Validation Retry (multiselect):
    Select notification(s) to call each time a domain validation step is retried.

5. Click on the save button.

You can edit Edit Policy or delete Delete Policy the DCV Policy.

A policy cannot be updated or deleted while it is actively running. Wait for the current run to complete, or cancel it first.

Only one execution per policy can be active or pending at a time. If a policy is already running or queued when a new trigger arrives (via cron or API), the new trigger is rejected.

License Limit

Horizon enforces a license-based cap on how many domains can be validated concurrently within a single policy run. Domains are dispatched in order at run start up to the available license slots. Domains exceeding the limit are immediately moved to the Skipped state and are not processed during that run.

A license slot is held for the full duration of a domain’s validation, including retries. Slots freed by completed domains are not reallocated mid-run. Skipped domains remain in the Provider’s list and will be picked up on the next scheduled execution if they still fall within the renewal window.