Encrypt DNS and give each query a clear route
DoH carries DNS queries and responses over HTTPS. By default, godusevpn sends remote DoH through the proxy, making DNS transport part of the proxy connection process. Local resolution and node-domain lookups follow their own purpose, configuration and protection state, coordinating the resolver with the actual network path.
That coordination makes everyday setup more coherent. Users do not have to assemble encrypted DNS, proxy bootstrapping and routing configuration separately, then wonder whether they work together. The client generates these relationships together, and its interactive explanation can show the application query, core decision and DNS exit as distinct steps.
fake-ip keeps domains associated with connections
fake-ip assigns a controlled virtual address to a domain. The core uses the mapping to identify subsequent connections. Together with TUN, this lets captured application traffic remain associated with its domain before the relevant routing rules apply. Domains, destination addresses and final exits become one traceable process.
When IPv6 is disabled by default, godusevpn uses IPv4 fake-ip alongside ipv4_only DNS, rejection of IPv6 destinations and explicit dropping of IPv6 traffic captured by TUN. Address mapping does not provide encryption itself. Encrypted transport, mapping and traffic capture each have a clear job within the connection.
DNS behaviour follows the selected routing mode
Rule mode chooses a proxy, direct access or rejection through rule groups and a default policy; DNS handling must fit the request’s purpose. Global mode sends ordinary application traffic through the proxy. With strict Global-mode protection enabled, configurations such as local system resolution receive the appropriate encrypted bootstrap handling.
Remote DNS, local DNS and node-domain lookups serve different roles. DoH therefore does not mean every query necessarily travels through the same tunnel. godusevpn places these responsibilities within a configurable, explainable connection system, so users can see what their current mode changes and which path a query follows.
Make complex relationships understandable in use
For everyday use, import a compatible sing-box JSON subscription and adjust modes or rules as needed. The client extracts node outbound definitions and combines them with its own settings to generate DNS, TUN and routing configuration. The subscription supplies available exits; the client organises local traffic and protection around them.
When troubleshooting, connection status, logs and the DNS path help explain the result. The website’s lab also lets users change query purposes and protection conditions to inspect the corresponding behaviour. Users should not need to maintain every technical detail manually, but settings that change network behaviour should remain understandable.