New PIHole DNS working but not filtering

[dave2318]

Please follow the below template, it will help us to help you!

Expected Behaviour:

Clients get filtered internet and show up on the admin console

Actual Behaviour:

Clients don't get filtered internet and don't show up on the admin console

Debug Token:

https://tricorder.pi-hole.net/rd11zpax9b!

I have Setup PIHole and set a laptop to use it's IP address for DNS.
Locally filtering is working and the localhost is showing up.
PIHole IP is 172.16.0.232
DNS is set on my laptop to 172.16.0.232 and DNS IS resolving but it's not showing up in the logs on PIHole.
if i nslookup pi.hole 172.16.0.232 i get:
Server: UnKnown
Address: 172.16.0.232

*** UnKnown can't find pi.hole: Non-existent domain

[jfb]

Your debug log shows that Pi-Hole is working properly and has received and responded to DNS queries in the 24 hours prior to the time shown belos:

   [2019-03-03 21:58:49.164 8465] Imported 196 queries from the long-term database
   [2019-03-03 21:58:49.164 8465]  -> Total DNS queries: 196
   [2019-03-03 21:58:49.164 8465]  -> Cached DNS queries: 87
   [2019-03-03 21:58:49.164 8465]  -> Forwarded DNS queries: 105
   [2019-03-03 21:58:49.164 8465]  -> Exactly blocked DNS queries: 4
   [2019-03-03 21:58:49.164 8465]  -> Unknown DNS queries: 0
   [2019-03-03 21:58:49.164 8465]  -> Unique domains: 23
   [2019-03-03 21:58:49.164 8465]  -> Unique clients: 2
   [2019-03-03 21:58:49.164 8465]  -> Known forward destinations: 2

The IP address 172.16.0.232 is tied to the wlan0 interface on the Pi (wireless). Is the Pi actually connected to the network via wireless or is the Pi connected via ethernet?

[dave2318]

Hi, yes it's connected wirelessly whilst I test.
I actually found the problem late last night but didn't get chance to update. My WiFi was forcing opendns on all connections, turned that of and it's working a treat!

Thanks
Dave