Keywords describe what to match; policies describe what to do when a match is found. The examples below illustrate syntax only and are not a complete rule set you can use to replace an existing configuration.
Rule
A Rule usually includes a match type, match value and handling policy. Rules are generally checked from top to bottom, so a broad entry near the top may prevent a more specific one below from taking effect. When troubleshooting, check which rule matches first rather than just confirming that a domain appears in the list.
DOMAIN
This keyword matches an exact domain, for example DOMAIN,example.com,DIRECT. It does not automatically include all subdomains or treat a URL path as part of the domain. To match both a root domain and its subdomains, understand the scope of DOMAIN-SUFFIX before choosing the rule.
DOMAIN-SUFFIX
This keyword matches a specified domain and its subdomains, for example DOMAIN-SUFFIX,example.com,PROXY. It matches at domain suffix boundaries; it does not match any occurrence of the same text. Do not include https:// or a page path in the match value.
GEOIP
This keyword matches according to how the destination IP is classified in a geolocation database, for example GEOIP,CN,DIRECT. The match is based on the destination address used for the connection and the database, not the website’s language or registration details. Content delivery networks and changing IP allocations can affect classification, so this is not a definitive judgment of a website’s identity.
IP-CIDR / IP-CIDR6
These two keywords match IPv4 and IPv6 address ranges respectively. The prefix length after the slash determines the range. For example, IP-CIDR,192.168.0.0/16,DIRECT matches this IPv4 range. These rules match IP addresses; they do not automatically track every future address associated with a domain.
FINAL
This is a fallback entry used when none of the preceding rules match, for example FINAL,PROXY. It usually belongs at the end of the rule list; otherwise, it may catch connections before later rules can handle them. Changing it affects every destination not covered by an earlier rule, so check the intended routing behavior before editing.
PROXY
This is a proxy policy marker in a rule. Matching connections use the proxy route, but the result still depends on the current selection and whether the relevant server is available. A PROXY match does not guarantee the destination can be reached. This is a rule outcome, not the overall Proxy mode in Global Routing.
DIRECT
This is a direct policy marker in a rule. Matching connections reach their destinations without using a proxy server. The device still needs a working local network and suitable name resolution. A connection using DIRECT does not mean the client as a whole is in Direct mode; other connections may match different policies.
REJECT
This is a reject policy marker in a rule. It blocks matching connections. An overly broad match may also affect resources that normal pages depend on, so do not add a broad rule based on an ambiguous name. If some content disappears afterward, check the match records and rule order before deciding whether to narrow the scope.