Routing rule
A routing rule links match conditions, such as a domain, IP, or port, to a target outbound. Rules are checked in order, so if a broad rule matches first, later rules won't process the same connection. If a rule appears not to work, check both its order and the destination information the core actually received.
Traffic routing
Traffic routing sends different connections through direct, proxy, or block outbounds. It determines the path a connection takes; it does not split a download across multiple nodes. If an app's traffic is not captured by the system proxy or a virtual interface, it won't enter the core's routing process.
GeoIP
GeoIP provides IP address range classifications for routing, often used to identify private addresses or group public ranges by region. Rules check whether the destination address falls within a dataset. A matching regional label does not identify the user's location or show that the service operator is in that region.
GeoSite
GeoSite provides domain collections organized by labels for use in routing rules. Which labels exist and which domains they contain depend on the data file actually loaded by the client. If the core only sees the destination IP and has not obtained the domain, it cannot match that IP directly against a domain collection.
FakeDNS
FakeDNS assigns a synthetic address during DNS resolution and stores the mapping between that address and the original domain. When an app connects to the address, the core can recover the domain after capturing the connection and continue routing. The synthetic address is not the actual service address; connections may fail if they take a path that cannot access the mapping.
DNS leak
A DNS leak occurs when queries are sent to a resolver outside the intended path. Before deciding whether one occurred, establish which resolver should handle each domain and which outbound the queries should use. Even if a web request takes the expected route, that alone does not show how its DNS query was routed.
Domain strategy
The domain strategy in routing determines whether to resolve a domain so IP rules can be tried. For example, IPIfNonMatch checks the available destination information first; if nothing matches, it resolves the domain and tries the IP conditions. If the same field name appears in an outbound or DNS module, interpret it in the context of that configuration layer.