I've digged a little bit further. if I use the pihole IP as DNS in Win10 (x64, build 14393.351), there is no entry on /var/log/pihole.log, which seems to indicate, that the DNS request never arrives at the pihole box. If i change it to something other know to work (either my ISPs resolver or google or the DNS of my fritzbox, it works instantly.
ipconfig /flushdns
ipconfig /registerdns
NETSH winsock reset
NETSH int ipv4 reset
NETSH int ipv6 reset
did absolutely nothing in terms of helping. I've also tested different browser, just to be sure its an OS problem (Egde, ie, FF), but i knew that beforde as a simple nslookup doesn't work.
My Router (a Fritz!Box 7490) has a DNS rebind protection, but this would also affect any other machine on my LAN, so this can't be it too.
Debug Log looks fine too, just gets no hits from any of my Win10 installs. (debug token is : tux1ksrbsj)
On my gamingbox 192.168.178.20 (just 1 physical NIC, fixed IP) it works when I completely disable the windows firewall. On the other 2 Systems (both laptops with 1x nic + 1x WLAN, DHCP) this doesnt help.
after a reboot of the gamingbox it doesnt work anymore, with firewall completely off. I reactivated it and redeactivated it (followed by a reboot each) but no 192.168.178.2 times out for DNS.
I even uninstalled any Avira antivirus snakeoil things. no luck anymore.
It worked exactly once on one of 3 Boxes, as I've desribed above (doublechecked it using nslookup on cmd line). Now im completely confused. My best guess is that it has something to do with Windows firewall / network stack
well if other devices work then it must be something wrong with your windows machines.
can you reply after you solved your problem please? i would like to know why it didnt worked.
for the sake of the reboot i've even rebooted te router now. And all my windows machines. result as expected: nope.
I wont reboot my gamingbox anymore as im writing from here atm, but I did with a laptop. linux works just fine, if i boot the windows on the same machine, meeep, no dns. same for all mobiles on my LAN: no problems.
interesting that it actually DID work a short time after diabling the firewall. but only once, on one machine. Either all my windows machines here are infected somehow or windows 10 network stack is a true mess.
as i wanted to reinstall this laptop anyway i will do a clean new win10 install.
sure as i said anything on my network is alright. I'm truly an experienced computer user
Also, pihole has happily discarded 256 ads since last reboot, which is completly amazing.
Thx for the input. I'll setup pihole on my second raspi tonight, if this doesnt help, we have loads of different routers in the office, for a next step in testing.
What I think it's strange is that only Windows is concerned and I don't see why a router should treat different OS differently, so I guess its something within windows or the pihole install.
i think I've tracked the problem down. I was runnung teamviewerd on the other raspi. I've disabled the daemon on the old raspi and now the old one is working fine for all devices including win10
interesting that this struggling daemon has only affected windows machines. which also had teamviewer installed.
my conclusion: teamviewer is generally a bad idea.
