Rule keywords & policies
DOMAIN
DOMAIN matches an exact domain name. For example, DOMAIN,example.com,DIRECT applies only to that domain and does not automatically include its subdomains. Enter a domain, not a full URL with a path. A website may request multiple domains, so check request logs to see which destination matched rather than relying only on the address bar.
Rule keywords & policies
DOMAIN-SUFFIX
DOMAIN-SUFFIX matches on a domain suffix boundary. Entering example.com typically covers the domain itself and its subdomains. It does not search for matching text anywhere in a URL or match paths. A request will not reach this rule if an earlier rule already matched, so check rule order after adding it.
Rule keywords & policies
GEOIP
GEOIP matches a destination using an IP geolocation database, for example GEOIP,CN,DIRECT. Results depend on the database and the resolved address; they do not indicate a website's language, account region, or operator location. A domain using a CDN may resolve to different addresses, so note the actual destination IP when troubleshooting.
Rule keywords & policies
IP-CIDR
IP-CIDR matches IPv4 addresses using network notation. The number after the slash is the prefix length; 192.0.2.0/24 is an example range for documentation. Use IP-CIDR6 for IPv6 ranges; the two formats cannot be used interchangeably. A domain may resolve to different addresses and match different rules, so check the DNS result as well.
Rule keywords & policies
FINAL
FINAL handles requests that did not match earlier rules and is usually placed at the end of the rule list. FINAL,PROXY and FINAL,DIRECT specify different final routes; there is no one setting that fits every configuration. If many requests unexpectedly use the final policy, check the scope and order of the preceding rules first.
Rule keywords & policies
PROXY
PROXY is a policy name in rules that selects the proxy route. The actual egress depends on the current selection and configuration. It is neither a server address nor a protocol name. A PROXY match tells you the handling direction; to confirm whether the connection succeeds, check the selected server, authentication, transport, and DNS.
Rule keywords & policies
DIRECT
DIRECT sends matched requests over the direct route, typically for destinations accessed through the current local network. It does not bypass all DNS processing or guarantee that the destination is reachable. DIRECT in a rule applies to matching requests; Direct in Global Routing is an overall mode. Be clear about which level you are checking.
Rule keywords & policies
REJECT
REJECT blocks requests matched by a rule. Its scope depends on the domains, addresses, or other conditions the rule can identify. A single domain may serve different kinds of content, so an overly broad rejection can disrupt normal features. If part of a page is missing, check the match log and narrow the rule instead of expanding the reject list.