I am only saying this because all I get to do with the phone is select the WAP name, enter the password and it connects.
There is on entering DNS, IP range, or anything else.
As the laptop (XP) connected and obeyed the DNS setting of PiHole, that implies to me that that side of things is working.
So only by eliminating everything else am I speculating on that which is not really liked or wanted.
I feel I may have to get back up to speed with wireshark.
IMHO, rebooting your router is a much quicker and easier first step than wiresharking. If it doesnât help things, then move on to more complex troubleshooting.
From a client device, if you go to https://www.dnsleaktest.com and choose the standard test, it should tell you which DNS resolver is answering for that client. Thatâs a quick way to find out if your client is reaching for DNS other than what your pi-hole is configured to use.
Okay, so Quad9 DNS rides on WoodyNet* infrastructure. That does indicate your client is using Quad9. Now do you see queries from that client IP showing in your pi-hole admin console?
(*History of âWoodyNetâ and PCH [Packet Clearing House] here)
Have you restarted this Samsung tablet? If not, try that and see if it starts showing up in your pi-hole dashboard...
Or an alternate test would be to try going to some very obvious URL (www.lego.com or something) on your tablet and immediately refresh your pi-hole dashboard. Confirm if you see that URL show up in the logs on the dashboard.
It really sounds like your tablet is just hanging on to your Linksys router IP as the DNS server from the previous DHCP lease it obtained. Your DNS queries appear to be going through the pi-hole, but getting there by way of the router in the middle. Restarting should cause your tablet to refresh its lease and pick up the Pi-hole IP from your current DHCP settings.
Sounds like a good plan. I think I saw where your DHCP lease time is 1440mins, so 24 hours. By design, your clients will renew their DHCP lease at 1/2 lease time, so 720mins (12 hours). By that point, all clients should pick up the pi-hole IP address from the DNS configuration in your DHCP advertisement.
I did not see the message yet, but will look shortly. Looking forward to seeing how things look in a couple hours.
Well the tablet hasn't (probably) been on the network since I installed PiHole and that was more than 720 minutes ago.
Yeah, tomorrow..... tomorrow..... tomorrow...... (Gee, you are lucky you can't hear me sing.)
Alas it is Sunday night the scheduled power outage, and alas Monday morning I am bugging out for 2 weeks to do other things. ARGH! If it is not one thing: it is another.
Well your TV's IP can be denied internet access at the router, but your TV can make DNS queries to an INTERNAL DNS server (which obviously is the case with your pi-hole) and the pi-hole is the device making the upstream DNS request to the Quad9 servers on the internet. So therefore, your TV still can't access the IP(s) that are returned by the resulting DNS query, but the scenario is perfectly valid and is not indicative of a configuration issue at this point.
As an aside, my Samsung TV likes to call out to all sorts of weird tracking domains, which I am not okay with. So I actually just block those domains in my pi-hole so the pi-hole responds to those queries with a nearly instant 0.0.0.0 or :: response to keep those queries from even consuming any internet bandwidth at all. That's another option you may want to consider.
If want to know what DNS server(s) your pads and phones are using, install a network info app on that device.
You might want to install a couple to compare as I've seen some network info apps to report wrong info.