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.
1 Like
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
Update:
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.)
Could you please provide another screenshot of the dashboard's Top Clients?
This would imply that your Laptop is acting as expected, using Pi-hole as DNS as provided via DHCP.
Can you confirm that you did connect your laptop wirelessly through your WAP?
I hope so! 
There is no cat-5 cable plugged into it.
Unfortunately, that would leave no hints at why other devices on your network seem to use your gateway as DNS server.
A separate device, aggregating and forwarding DNS traffic to your gateway, could still explain that. Which brings me back to my previous yet unanswered question:
(Sorry, I thought I had answered that)
The WAP and router (192.168.0.254) are the same device.
CISCO 1900 ACS