Lines Matching defs:policy
36 * Parallel radix trees for databases of response policy IP addresses
39 * policy addresses by representing the two sets of IP addresses and name
47 * name server IP address policy sub-zone (or both) of the corresponding
48 * response policy zone. The policy data such as a CNAME or an A record
49 * is kept in the policy zone. After an IP address has been found in a radix
50 * tree, the node in the policy zone's database is found by converting
54 * The response policy zone canonical form of an IPv6 address is one of:
105 * client-IP, IP, and NSIP policy triggers.
128 * QNAME and NSDNAME policy triggers.
137 * The data in a RBT node has two pairs of bits for policy zones.
191 dns_rpz_policy_t policy;
209 return (tbl[n].policy);
215 dns_rpz_policy2str(dns_rpz_policy_t policy) {
218 switch (policy) {
382 * and qname_skip_recurse (a bitfield indicating which policy
388 * has to have bits set for the policy zones for which
397 * triggers in policy zones listed after other zones
411 * But going by the description in the ARM, if the first policy
435 * non-error response. So, in the order of listing of policy
436 * zones, within the first policy zone where recursion may be
437 * required, we should first allow CLIENT-IP and QNAME policy
442 * Get a mask covering all policy zones that are not subordinate to
443 * other policy zones containing triggers that require that the
661 * to its canonical response policy domain name without the origin of the
662 * policy zone.
745 * Determine the type of a name in a response policy zone.
770 * Convert an IP address from canonical response policy domain name form
969 * real policy zone where wildcards will be handled.
1367 * We need a summary database of names even with 1 policy zone,
1397 * Get ready for a new set of policy zones for a view.
1451 * Free the radix tree of a response policy database.
1483 * Discard a response policy zone blob
1528 * Forget a view's policy zones.
1596 * This is also the most common case of policy zone loading.
1597 * Most policy zone maintenance should be by incremental changes
1680 "(re)loading policy zone '%s' changed from"
1781 * Unless there is only one policy zone, copy the other policy zones
1782 * from the old policy structure to the new summary databases.
2043 * We need a summary database of names even with 1 policy zone,
2149 * policy zone relevant to a triggering IP address.
2151 * return the policy zone's number or DNS_RPZ_INVALID_NUM
2273 * Search the summary radix tree for policy zones with triggers matching
2340 * Translate CNAME rdata to a QNAME response policy action.
2371 * A qname of www.evil.com and a policy of