Routing and DNS
First ask which resolver handles the domain, then which outbound handles the connection. These steps are related, but changing one doesn’t necessarily change the other.
Match criteria
Routing rule
Routing rules match traffic by criteria such as domain, destination IP, or port, then send matching traffic to a specified outbound. The core usually checks rules in order, and the first match determines where traffic goes. If a specific rule doesn’t take effect, check whether it appears after a broader rule that matches first.
Rule data
GeoIP
In routing configurations, GeoIP usually refers to tagged IP range data used to match destination IPs. These classifications come from the data set; they aren’t real-time location lookups and don’t match by domain suffix. If the destination is a domain, whether it’s resolved before matching against an IP depends on the core’s routing policy.
Rule data
GeoSite
GeoSite is a collection of domains organized by tags for use in routing or DNS rules. The current data file determines which domains each tag covers; don’t infer the full list from the tag name alone. If a particular domain doesn’t match as expected, check whether it’s in the collection, then review the rule order.
See what GeoIP matches →
Outbound selection
Split tunneling
Split tunneling routes different requests through different outbounds according to rules—for example, sending local network traffic through a direct outbound. It doesn’t change the server’s configuration. To troubleshoot a destination, check both whether the app handed its traffic to the client and which rule the client applied to that traffic.
Domain mapping
FakeDNS
FakeDNS returns a synthetic IP for a domain and stores the mapping between that IP and the original domain in the core. When an app connects to that address, the core can use the mapping to recover the domain and apply domain-based rules. The synthetic address isn’t the website’s real IP, so it shouldn’t be used to test a direct connection to the server.
Resolution path
DNS leak
A DNS leak occurs when domain lookups take an unexpected route—for example, when queries still go to a resolver provided by the local network while web traffic uses a proxy. To investigate, first identify which resolver should handle the queries, then check the browser’s, system’s, and client’s DNS settings separately. A change in the web traffic’s exit IP alone doesn’t show where DNS queries went.
See how DNS routing works →