DOMAIN-SUFFIX
DOMAIN-SUFFIX matches a domain suffix, making it useful for applying the same action to a domain and its related subdomains. Confirm that the scope is what you intend. Do not infer the request domain from a page’s display name; use the demonstration domain to understand the syntax.
DOMAIN-SUFFIX,example.com,PROXY
DOMAIN-KEYWORD
DOMAIN-KEYWORD checks whether a domain contains a specified text string, and may match more broadly than an exact domain rule. A common keyword may also match unrelated domains. Before adding one, identify what you intend to match and verify the result in Config.
DOMAIN-KEYWORD,example,DIRECT
GEOIP
GEOIP matches based on geographic IP data for the destination, not the language of a webpage or the domain suffix. The resolved address and data used can affect the result. To match a specific domain precisely, distinguish GEOIP rules from domain-based rules.
GEOIP,CN,DIRECT
IP-CIDR
IP-CIDR matches requests by IPv4 address range; the number after the slash indicates the range size. It matches addresses, not domain text. When troubleshooting, first confirm the address the destination resolves to, then check whether the rule’s range should match it.
IP-CIDR,192.0.2.0/24,DIRECT
FINAL
FINAL is the fallback for requests not handled by earlier rules and is usually placed at the end of the rule list. It determines what happens to all remaining requests, so changing one domain rule may not explain the results for all traffic. When checking a configuration, read through to the last line.
FINAL,DIRECT
PROXY · DIRECT · REJECT
These three uppercase terms are actions at the end of a rule: PROXY sends the request through the specified proxy, DIRECT connects directly, and REJECT denies the request. They describe what happens when a rule matches and are distinct from the three overall options at the top of Global Routing. Before writing a rule, decide how matching requests should be handled.