mirror of
https://github.com/v2rayA/v2rayA.git
synced 2026-11-20 23:02:25 +03:00
Node hostnames, upstream hostnames and the service's own lookups (subscriptions, latency tests) were resolved by hard-coded public resolvers (223.5.5.5, 119.29.29.29, ...) whatever the DNS rules said; the second nameserver written into the hijacked /etc/resolv.conf was hard-coded too. directDnsServers() now collects the plain udp/tcp IP upstreams of the rules with the direct outbound, and - resolv.PreferredServers hands them to the service's resolver before its public list - the module's bootstrap_dns is the system's resolvers plus those upstreams - the upstream for node hostnames is the first of them - HijackResolv writes the first port-53 one as the second nameserver, and so does the restore when no backup exists getSystemDnsServers reads the backup while resolv.conf is hijacked, so a restart no longer hands the module its own listener as bootstrap.