Welcome to the community! Read our posting tips, and learn how to earn ranks, levels and badges to get started.
Ask any devices or smart home question in the Devices/Security or Network Troubleshooting Categories.
Happy posting!
Ask any devices or smart home question in the Devices/Security or Network Troubleshooting Categories.
Happy posting!
Fing Desktop Beta: DNS Failures




Fing desktop (v0.5.27) consistently reports failed DNS lookups. I'm using Pihole as my local DNS server, and I see the requests successfully forwarded by Pihole, but Fing Desktop still reports the lookup as failing.
EDIT: The app just updataed to v0.6.0 and the behavior is the same -- DNS tests still fail.
Tagged:
0
Answers
To be 100% sure we installed in lab and tested both from Mac and from Windows, and the health check works good.
You should check your pi-hole configuration maybe.
Carlo from Fing
In the latter, maybe it's going to the secondary. Moreover we saw that pi-hole shows active devices sending data, in one of the left menu sections, maybe you can check there if this windows laptop is correctly using or having issue.
We did test with Windows 10 Pro as well.
Carlo from Fing
I agree with @Carlo_from_Fing it could be your network has some conflicts with the DNS its dishing out I would suggest removing any secondary ones.
It’s apparently something to do with Windows. Resolution from the Command prompt behaves similarly, and it seems to happen on two Windows 10 systems on my network (haven’t checked a third yet).
I have only one Pihole, but it’s configured as both primary and secondary in the router. The Windows laptop is configured to get DNS from the router, and the Fing Desktop only has issues when using Pihole. If I set it to use Cloudflare it works fine.
I haven’t really played around with it much yet, but I’ll report back if/when I figure it out.
EDIT: I’m guessing I still have an issue... nslookup from my Windows Command prompt is still timing out:
1) try pinging your redacted dns from cmd (i.e. ping 192.168.x.x) - if it fails dump a ipconfig /all
2) if you get a response, try disabling pihole from the pihole gui and try the nslookup again
3) if its still failing then can you screenshot your dns settings from pihole as I think the problem will lie there.
I haven’t had time to play with it much, but I’m pretty confident the issue is with my Windows systems, not Pihole. If I connect one of my Windows 10 systems to a VPN, nslookup from the command line still fails:
See mine below:
Do you have any manual setup is windows for your adapter? Also are you only connecting on one adapter (I.e wired or wireless not both)?
and ipconfig /all dump would be helpful