Trying to install wireguard - Checking DNS resolver failed Topic is solved

Having issues with your DietPi installation or found a bug? Post it here.
Totila
Posts: 56
Joined: Sun Aug 04, 2019 8:29 am

Re: Trying to install wireguard - Checking DNS resolver failed

Post by Totila »

I havent set any specific DNS in my phone (stats certainly show that my PI is being used as only DNS when I am on Wifi, I cannot check that when I am on mobile data though).

Turns out, google chrome and vivaldi show two DNS servers checking with https://www.perfect-privacy.com/de/tests/dns-leaktest

Firefox only shows my public IP and therefore blocks ads as expected when I am on mobile data.

So, Chrome and chrome-based phone browsers are bad as they use hard-coded DNS servers it seems.

Can you confirm your end? Which browser are you using?
User avatar
Joulinar
Posts: 4823
Joined: Sat Nov 16, 2019 12:49 am

Re: Trying to install wireguard - Checking DNS resolver failed

Post by Joulinar »

Not sure if this is really a good test. Anyway, on my mobile it doesn't matter if I use Chrome, Edge or Firefox. Ads are blocked on all my Apps and browser.

Maybe some setting in Chrome. Probably you could try to reset the app like delete data, delete temp data, try to uninstall updates as much as possible. Once done install it from play store again.
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
Totila
Posts: 56
Joined: Sun Aug 04, 2019 8:29 am

Re: Trying to install wireguard - Checking DNS resolver failed

Post by Totila »

Not sure if this is really a good test
What is a good test then?

I set chrome to factory default (and reinstalled) and still same result. Ads are not being blocked, tcpdump doesnt show any output.

I am on Android 9 (fwiw)
User avatar
trendy
Posts: 314
Joined: Tue Feb 25, 2020 2:54 pm

Re: Trying to install wireguard - Checking DNS resolver failed

Post by trendy »

Totila wrote: Mon Jun 07, 2021 10:57 amPihole listens on all interfaces
And must permit all origins, because the android client is more than a hop away.
Also make sure that the browsers are not using hardcoded DNS or DNS over HTTPS
Totila
Posts: 56
Joined: Sun Aug 04, 2019 8:29 am

Re: Trying to install wireguard - Checking DNS resolver failed

Post by Totila »

And must permit all origins, because the android client is more than a hop away.
I did but that didnt change anything unfortunately.
Also make sure that the browsers are not using hardcoded DNS or DNS over HTTPS
How would I do that?
I only know that firefox 'seems' different to chrome as on firefox ads are being blocked. I didnt find a settings on chrome to disable any predefined DNS (if google would even present that to the user)
User avatar
trendy
Posts: 314
Joined: Tue Feb 25, 2020 2:54 pm

Re: Trying to install wireguard - Checking DNS resolver failed

Post by trendy »

It would help to troubleshoot a bit. Install tcpdump and verify that you can see packets in and out.
tcpdump -evn udp port 53 try to resolv something from the android, then hit Ctrl-c, copy the output and paste here.
Firefox also has an option to use DNS over HTTPS and it is visible under proxy settings.
Totila
Posts: 56
Joined: Sun Aug 04, 2019 8:29 am

Re: Trying to install wireguard - Checking DNS resolver failed

Post by Totila »

I resolved https://dietpi.com
There was NO terminal output using google chrome on my Android (on mobile data).

Using Firefox gave me this:

Code: Select all

12:04:18.210314 b8:27:eb:cd:43:a1 > 2c:3a:fd:25:52:bf, ethertype IPv4 (0x0800), length 81: (tos 0x0, ttl 64, id 51864, offset 0, flags [none], proto UDP (17), length 67)
    192.168.200.2.10697 > 173.245.59.176.53: 57555% [1au] A? dieTpi.cOm. (39)
12:04:18.228748 2c:3a:fd:25:52:bf > b8:27:eb:cd:43:a1, ethertype IPv4 (0x0800), length 219: (tos 0x0, ttl 58, id 43469, offset 0, flags [DF], proto UDP (17), length 205)
    173.245.59.176.53 > 192.168.200.2.10697: 57555*- 3/0/1 dieTpi.cOm. A 172.67.173.4, dieTpi.cOm. A 104.21.96.47, dieTpi.cOm. RRSIG (177)
12:04:19.312236 b8:27:eb:cd:43:a1 > 2c:3a:fd:25:52:bf, ethertype IPv4 (0x0800), length 81: (tos 0x0, ttl 64, id 47404, offset 0, flags [none], proto UDP (17), length 67)
    192.168.200.2.33236 > 173.245.58.167.53: 10152% [1au] A? DiEtpi.CoM. (39)
12:04:19.324875 2c:3a:fd:25:52:bf > b8:27:eb:cd:43:a1, ethertype IPv4 (0x0800), length 219: (tos 0x0, ttl 58, id 37310, offset 0, flags [DF], proto UDP (17), length 205)
    173.245.58.167.53 > 192.168.200.2.33236: 10152*- 3/0/1 DiEtpi.CoM. A 104.21.96.47, DiEtpi.CoM. A 172.67.173.4, DiEtpi.CoM. RRSIG (177)
I couldnt find any proxy settings on the android firefox.
User avatar
Joulinar
Posts: 4823
Joined: Sat Nov 16, 2019 12:49 am

Re: Trying to install wireguard - Checking DNS resolver failed

Post by Joulinar »

Well we are running in circle. I guess we already know that some apps seems to use a different DNS than other apps. But this is something special on the client/mobile device. And honestly, I don't know how this is possible. On my Android mobile device this is not the case.

In fact, Wireguard is working as server, PiHole is accepting the request but due to whatever reason Chrome mobile app is using a different DNS than the one specify in the Wireguard client.
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
Totila
Posts: 56
Joined: Sun Aug 04, 2019 8:29 am

Re: Trying to install wireguard - Checking DNS resolver failed

Post by Totila »

Then let's leave it here.

Many thanks for your efforts. Much appreciated. At least the home setup is working flawlessly.

Some things will remain a mystery.

Thanks again.

T
User avatar
Joulinar
Posts: 4823
Joined: Sat Nov 16, 2019 12:49 am

Re: Trying to install wireguard - Checking DNS resolver failed

Post by Joulinar »

probably you have another mobile device you can test on.
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
Post Reply