Routing rule
Routing rules select an outbound for traffic based on conditions such as domain, destination address, and port. The core checks rules in configuration order, and the first match determines where traffic goes. Broad rules placed first may prevent more specific rules later in the list from matching.
Traffic routing
Traffic routing sends different traffic already received by the core to different outbounds. For example, LAN destinations can go direct while other matched requests use a specified proxy. If an app's traffic never reaches the local proxy or virtual interface, changing the core's routing rules won't affect that app.
Outbound tag
An outbound tag is the name identifying an outbound in the configuration; routing rules use it to select that outbound. Common tags such as direct, proxy, and block are naming conventions; behavior depends on the outbound configuration assigned to each tag. Renaming an outbound to block does not automatically block requests.
GeoIP
GeoIP is a collection of IP address ranges grouped by category, used by routing rules to match destination addresses. For example, geoip:private can match private and reserved address ranges defined by the rule set. If the core receives a domain, whether it resolves it to an IP for matching also depends on the domain resolution strategy.
GeoSite
GeoSite is a collection of domain rules grouped by category, commonly supplied by geosite.dat. geosite:cn refers to the cn category in the current rule set; it does not mean every listed domain resolves to the same region. If a rule does not match, first check that the category exists and that the core received the destination domain.
Domain resolution strategy
In a routing configuration, domainStrategy determines whether domain requests are resolved to IP addresses when matching routing rules. For example, IPIfNonMatch lets the core resolve a domain after the initial match fails, then use the resulting IP to check the rules. This setting does not specify an upstream DNS server.