Yeah, I think I have addressed this problem yesterday. All the devices pointed to the router/wap as their DNS. That obfuscated who was doing what.
So I set the devices to use PiHole as the DNS.
This device is wireless and so I can't set the DNS AFAIK. I just point to the WAP.
This is what the router config looks like:
192.168.0.83 is PiHole
I rebooted the machine and still getting an error when I go to tools/network.
For the sake of it, this is the /etc/hosts file:
192.168.0.1 blacksheep
192.168.0.6 NUC
192.168.0.9 TV
192.168.0.21 Relay-Board
192.168.0.22 Bauhn-1
192.168.0.23 Arlec-1
192.168.0.24 Arlec-2
192.168.0.25 Bulb-1
192.168.0.26 Bulb-2
192.168.0.27 IR-Hub
192.168.0.34 WIB
192.168.0.38 Lappy
192.168.0.81 XBMCPi
192.168.0.82 MusicPi
192.168.0.83 BedPi
192.168.0.84 LCDPi
192.168.0.86 PiFace
192.168.0.89 EyeSpyPi
192.168.0.91 CameraPi
192.168.0.92 PortaPi
192.168.0.93 TelePi
192.168.0.94 BeefPi
192.168.0.99 TimePi
192.168.0.201 shed
192.168.0.200 outhouse
192.168.0.221 sub1
192.168.0.240 raspbx
192.168.0.253 Printer
192.168.0.254 gateway
127.0.0.1 localhost
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
127.0.1.1 BedPi
Your WAP is supplied by your router, or is it a different device?
That screen would imply you are already distributing Pi-hole as local DNS server via DHCP.
It may take clients some time until their DHCP lease expires before they pick up the new settings.
From your screenshot, this should happen within 1,440 minutes (a day), unless you did change and decrease that lease time only recently.
You may force a client to renew its lease, e.g. by dis- and reconnecting to the network or by power-cycling the device.
The device is only connected to the WAP when I want it. I don't leave it connected all the time.
So it reconnects to the WAP if/when I turn on its WiFi.
I can't see power cycling it doing much, as the WiFi is turned off when the transaction is complete.
I can't see the need to leave WiFi power to portable devices on all the time if not needed.
Executed on a client connected through the WAP, what's the output of:
nslookup pi.hole
nslookup flurry.com 192.168.0.83
(Edit: Almost forgot)
nslookup flurry.com 80.241.218.68
Sorry, you may need to draw me a map of what you want me to do.
Are those commands you want me to run?
(Does the WiFi device need to be connected when I do them?)
pi@BedPi:~ $ nsloopup pi.hole
-bash: nsloopup: command not found
pi@BedPi:~ $ nslookup pi.hole
Server: 9.9.9.9
Address: 9.9.9.9#53
** server can't find pi.hole: NXDOMAIN
pi@BedPi:~ $ nslookup flurry.com 192.168.0.83
Server: 192.168.0.83
Address: 192.168.0.83#53
Name: flurry.com
Address: 0.0.0.0
pi@BedPi:~ $
That is on/from PiHole.
Run these on the client, not the Pi.
Yes, those are commands that should be run from a terminal on a client machine.
And yes, that machine needs to be connected to your network.
That's going to be difficult as there isn't really a CLI on the tablet.
Tablets don't come with a CLI usually.
I may have a terminal app installed, but won't promise it.
If it's a tablet or mobile phone, then using a terminal app may not help in our case: Some of those apps are known to employ their own DNS servers, regardless of what the system provides, and that get's into the way of us trouble-shooting potential DNS issues.
It would help if you could connect a laptop or other device with a CLI to your WiFi network.
I'll see what I can do ITMT to get around it. Alas I don't think it is going to work.
My WiFi devices are a tablet, phone, and bulbs, power points etc. Not really having a CLI.
Let's jump back to the beginning. It looks like your Pi-hole does not see individual IPs on client requests, but only sees the IP of the router or WAP. If this is the case, then you will need to change this so you can see individual client IPs.
If this is not the case, then we need to verify that those clients are actually using Pi-hole, thus the request for the nslookup commands. Without a terminal, you can still load a web page on the client while tailing the Pi-hole log. If you don't see a burst of activity in the log tail while the client loads a page, that client isn't using Pi-hole.
Yes, I went down that yesterday when I had that problem. All devices pointed to the router for the DNS.
Then I just pointed the router to PiHole for DNS. Thus overwriting the IP addresses with the router's IP.
So I went around to the (for now) 4 devices and them to PiHole's IP address for DNS.
The tablet really didn't like me trying to install a terminal app.
Hang on. Something is happening with the Tablet.
Na, sorry. Still not wanting to play the game.
I may power up an old Laptop and see if it wants to play the game.
It would be good if you can.
The intention behind the three nslookup commands (I've added a third) is to establish that a WAP connected device does indeed receive Pi-hole as DNS and to ensure that your router/WAP/gateway is not redirecting DNS traffic.
Do those commands exist in the XP world?
If that's referring to Windows XP, then yes.
Ok, after the XP lappy booted and connected......
(Sorry I can't do a screen print.)
typed as best I can from looking at the lappy screen while typing:
DNS request timed out.
timout was 2 seconds
** can't find servername for address 192.168.0.254: time out
** Default servers are not available
Server: unknown
Address: 192.168.0.83
Name: pi.home
Address: 192.168.0.83
nslookup flurry.com 192.168.0.83
DNS request timed out.
timeout was 2 seconds.
** can't find server name of address 192.168.0.83: timed out
Server: Unknown
Address: 192.168.0.83
Name: flurry.com
Address 0.0.0.0
There is no way to set the DNS on the lappy.
Just the gateway.
It is connected by DHCP
I am not sure it is connected.
I can't even ping google or ping 8.8.8.8
The answers themselves seem ok, but time-outs for the name server reverse lookups are unusual.
What's the IP of that XP laptop?
Do you see that IP showing up in Pi-hole's Top Clients lists?
ipconfig:
192.168.0.153
I can ping this machine. Ok.
I can't seem to ping the router (192.168.0.254) or PiHole (192.168.0.83)
I can ping 192.168.0.99 - another Pi.
But I can't ping 192.168.0.93 - another Pi.
Yes I can see it in the IP list.
(Long term data / top lists then scroll down to the bottom of the screen.)