Defines a default count if {@code cases} is not defined for the rule or a matching case does not define {@code count}. {@code defaultCount} is not applied if {@code cases} is defined and there are no matching cases. In this scenario, the next rule will be processed. If no rules remain to be processed, the answer will be chosen from the remaining list of answers. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
A user-defined description of the rule's purpose or behavior.
An array of {@code caseConditions}. A rule may optionally include a sequence of cases defining alternate configurations for how it should behave during processing for any given DNS query. When a rule has no sequence of {@code cases}, it is always evaluated with the same configuration during processing. When a rule has an empty sequence of {@code cases}, it is always ignored during processing. When a rule has a non-empty sequence of {@code cases}, its behavior during processing is configured by the first matching {@code case} in the sequence. When a rule has no matching cases the rule is ignored. A rule case with no {@code caseCondition} always matches. A rule case with a {@code caseCondition} matches only when that expression evaluates to true for the given query.