Open SubZero5 opened 5 years ago
Why does the DNS resolving in android apps not working?
Is 8.8.8.8 accessible from your computer? For example, what is the result of:
dig @8.8.8.8 google.com
?
If not, you should set your custom dns using gnirehtet -d xx.xx.xx.xx
(replace xx.xx.xx.xx with your DNS server, which must be accessible from your computer).
I run gnirehtet with gnirehtet -d mo.de.ms.IP
and with gnirehtet -d IS.Ps.DNS.IP1
and gnirehtet -d IS.Ps.DNS.IP2
but still the dns does not resolve...
However I have working internet connection on my laptop.
I don't have dig
but I have nslookup and as I nslookup google.com mo.de.ms.IP
and with nslookup google.com IS.Ps.DNS.IP1
and nslookup google.com IS.Ps.DNS.IP2
the answers are similar and they all resolve OK...
Server: *** Address: mo.de.ms.IP / IS.Ps.DNS.IP1 / IS.Ps.DNS.IP2
Non-authoritative answer: Name: google.com Addresses: 2a00:1450:4017:80b::200e 172.217.169.206
How do I get a detailed and verbose debug log? :)
Is it possible that gnirehtet gets the first IPv6 and skip the second one somehow?
I myself added DNS in the program, so you can specify another 8.8.8.8 можно использовать DNS програмы для телефона! есть хорошие модули Xposed. Fake connect WiFi
you can use DNS programs for your phone! there are good Xposed modules. Fake connect WiFi
Hi @ars2005tron
Resolving DNS over the VPN is a must, system and app resolved DNS Queries are superseeded by the VPN connection... Meaning, any DNS Resolve requests are submitted thru the VPN connection...
SubZero5 --put the PROXIFIER on. IP tcp will go through SSH and DNS will go through VPN
Hi,
Why does the DNS resolving in android apps not working? Shouldn't it be resolved over the VPN connection of gnirehtet? Every other app other than the google stuff is being able to connect to the web sites.
I can not add a google account or browse the web? The error on the add account tab is An error occured/Trouble connecting to google servers. The error on the browser is net::ERR_NAME_NOT_RESOLVED
How to overcome this side effect?
The sites hosted on lP addresses work flawless: ie: http://104.27.184.45 opens up perfectly. But the DNS Resolver: ie: http://172.217.22.206 redirects to google.com but as google.com does not resolve, net::ERR_NAME_NOT_RESOLVED error comes up.