Domain name resolution
DNS
DNS looks up addresses and other records associated with domain names. The operating system, browser, and proxy core may each use different resolvers, so changing DNS in the client may not affect every app. To troubleshoot, first identify which component is making the query, then check its resolver and network path.
Virtual network interface
TUN mode
TUN mode receives IP traffic routed by the operating system through a virtual network interface, without requiring every app to read the system proxy settings. Which traffic enters the interface still depends on system routes, exclusions, and platform permissions. If local network access stops working after enabling TUN, check whether the relevant subnet is included in the routing scope.
Address mapping
FakeDNS
FakeDNS assigns a temporary mapped address to a domain. When an app connects to that address, a client or core with access to the mapping record can restore the original domain and then apply domain rules. This is not the destination server’s actual address; if the connection does not return to the component that created the mapping, it may fail.
Query path
DNS leak
A DNS leak occurs when a query takes a resolution path outside the intended policy—for example, when a query meant for a specified resolver is handled by the system default instead. Some apps have built-in DNS resolution, so their query paths may differ even when web requests use a proxy. Compare observed behavior with the intended policy rather than judging by the resolver’s name alone.