DOMAIN
Exact domain match
DOMAIN matches an exact domain. For example, DOMAIN,example.com,DIRECT applies to that domain itself. It does not automatically cover subdomains such as www.example.com; use DOMAIN-SUFFIX when you need to match subdomains. Enter a domain here, not a URL path or query string.
DOMAIN-SUFFIX
Match a domain and its subdomains
DOMAIN-SUFFIX matches a specified domain and its subdomains. For example, DOMAIN-SUFFIX,example.com,PROXY can match both example.com and www.example.com. It matches domain boundaries, not arbitrary strings. Put more specific rules first if a subdomain needs different handling.
DOMAIN-KEYWORD
Match a string in a domain
DOMAIN-KEYWORD checks whether a domain contains a specified string. It often matches more broadly than exact-domain and suffix rules. Short strings can catch unrelated domains, so avoid using a site abbreviation without checking its scope. If traffic is routed unexpectedly, check whether a broad keyword rule appears before a more precise rule.
GEOIP
Geolocation label for a destination IP
GEOIP matches labels in an IP geolocation database. For example, GEOIP,CN,DIRECT sends matching addresses to DIRECT. It checks the database’s classification of the destination IP, not the page language, company registration location, or content ownership. Database updates and a site’s content delivery network can change the result; add exact domain rules if needed.
IP-CIDR / IP-CIDR6
IPv4 and IPv6 address ranges
IP-CIDR is for IPv4 ranges, and IP-CIDR6 is for IPv6 ranges. The prefix length after the address determines the range. For example, IP-CIDR,192.0.2.0/24,DIRECT is a documentation example, not a single server address. Check which address family the destination uses to avoid handling IPv4 while missing IPv6.
FINAL
Fallback policy for unmatched requests
FINAL handles requests that did not match any earlier rule. For example, FINAL,PROXY sends the remaining requests through the proxy. It is usually placed at the end of the rule list; placing it too early prevents later rules from matching. Whether the fallback should be PROXY or DIRECT depends on the configuration’s purpose—there is no single answer for every network.
PROXY / DIRECT / REJECT
Policy applied when a rule matches
PROXY sends a request through a proxy, DIRECT connects directly, and REJECT denies the request. These values belong in a rule’s policy field. The uppercase policies are at a different level from the Proxy and Direct modes in Global Routing. REJECT can block requests based on conditions the rules can identify; it cannot distinguish every part of a page on the basis of a domain alone.