How matching works
A rule matches requests against specified conditions and assigns a handling policy. Rules are generally checked from top to bottom, and a matching request is handled according to the corresponding policy. Put narrower exceptions before broader rules. If a rule does not seem to work, first check whether an earlier rule has already matched the request.
Domain matching
DOMAIN-SUFFIX matches domain suffixes and is useful for covering a domain and its subdomains. For example, DOMAIN-SUFFIX,example.com,PROXY matches the example.com domain and routes it through PROXY. It does not match webpage paths or search for an arbitrary string within a URL.
IP geolocation
GEOIP matches an address based on its classification in a geolocation database, for example, GEOIP,CN,DIRECT. The database classification does not identify where a website operator is based and may change as addresses or database entries are updated. If the result is unexpected, check the actual destination IP and any earlier rules.
Network range matching
IP-CIDR and IP-CIDR6 match IPv4 and IPv6 address ranges, respectively. The prefix length after the slash determines the range covered. These rules match addresses, not domain-name text. If a domain resolves to multiple addresses, whether a request matches depends on the destination address actually used.
Fallback at the end
FINAL is the fallback rule used when no earlier rule matches, so it belongs at the end of the rule list. For example, FINAL,DIRECT sends requests not handled by earlier rules through DIRECT. Placing FINAL earlier prevents subsequent rules from being matched.
Handling policies
PROXY, DIRECT, and REJECT are rule policies meaning route through a proxy, connect directly, and reject the request, respectively. PROXY does not name a specific server; the route depends on the current selection and configuration. REJECT blocks matching requests but does not guarantee that every instance of a particular type of content will disappear from a page.
Domain name resolution
DNS resolves domain names to IP addresses and is one step in establishing many network connections. A resolution failure, a change in the resolved address, and a failure later in the connection are different problems. Changing DNS settings will not fix every authentication or connectivity issue; distinguish the resolution result from the actual request path when troubleshooting.