Open 1265578519 opened 1 year ago
we had a long running difficulty of making DNS on windows work in a way that it cannot leak out when exit tunneling is enabled. the l3-intercept
option hooks every single packet for udp/53 and tcp/53 and sends it to lokinet. despite this i have been getting reports that DNS on windows is STILL broken but using something like DNSCrypt-Proxy with a forward rule for .loki
and .snode
fixes this. this is likely because it tunnels upstream dns via something that isn't DNS (instead using tls).
i guess we can just bundle dnscrypt-proxy because i give up.
we had a long running difficulty of making DNS on windows work in a way that it cannot leak out when exit tunneling is enabled. the option hooks every single packet for udp/53 and tcp/53 and sends it to lokinet. despite this i have been getting reports that DNS on windows is STILL broken but using something like DNSCrypt-Proxy with a forward rule for and fixes this. this is likely because it tunnels upstream dns via something that isn't DNS (instead using tls).
l3-intercept``.loki``.snode
i guess we can just bundle dnscrypt-proxy because i give up.
Can it using openvpn? Openvpn work normal on the windows network dns. example sstap, netch and various network are using it as.
we were using that driver before but it has been deprecated for over a decade now. if you have the proper calls to netsh we need to call to set dns and not have it leak i want to know what those are.
log snode timed out dns not working v0.9.11 The computer version test 0.9.11 has a BUG, dns is hijacked and the domain name cannot be resolved, you need to modify the configuration file C:\ProgramData\lokinet\lokinet.ini, find l3-intercept and assign the value false, bind assign the value 127.0.0.1:54, and then use the browser doh option or AuroraDNS to System global DNS pollution