Local devices show ip an not name

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

Expected Behaviour:

Expect to see names not IP Address

Actual Behaviour:

Top Clients (total) and Top Clients (blocked only) show ip address not device names

Debug Token:

Your debug token is: https://tricorder.pi-hole.net/0oumdl5t9r

@Michael_Serowik Are the devices that are showing up in the Top Client lists on the same network subnet as your Pi-hole device? ... or are they on different VLANs?

Also,
can you post output for below on a client PC (Linux/Windows/MacOS) ?

nslookup pi.hole

And output for below on Pi-hole ?

cat /etc/resolv.conf

pi@Pi-Hole:~ $ nslookup pi.hole
Server: 8.8.8.8
Address: 8.8.8.8#53

** server can't find pi.hole: NXDOMAIN

pi@Pi-Hole:~ $ cat /etc/resolv.conf
nameserver 8.8.8.8

the are on the same vlan. I am not running any vlan's

Ok, that was not what I asked but it reveals some.
The /etc/resolv.conf file should contain below:

pi@noads:~ $ cat /etc/resolv.conf
nameserver 127.0.0.1

Or else the web part of Pi-hole wont be able to resolve IP's to names to be displayed on the web GUI:

pi@noads:~ $ nslookup 10.0.0.11
Server:         127.0.0.1
Address:        127.0.0.1#53

11.0.0.10.in-addr.arpa  name = hakpc.dehakkelaar.nl.

Could you run the nslookup again but this time on a CLIENT PC ?

*** From Client Machine ***

C:\Users\Dad>nslookup 192.168.1.254
Server: Pi-Hole
Address: 192.168.1.254

Name: Pi-Hole
Address: 192.168.1.254

C:\Users\Dad>nslookup pi-hole
Server: Pi-Hole
Address: 192.168.1.254

*** Pi-Hole can't find pi-hole: Non-existent domain

*** From Pi-Hole***
pi@Pi-Hole:~ $ cat /etc/resolv.conf
nameserver 127.0.0.1

pi@Pi-Hole:~ $ cat /etc/resolv.conf
nameserver 127.0.0.1

pi@Pi-Hole:~ $ nslookup 192.168.1.254
Server: 127.0.0.1
Address: 127.0.0.1#53

254.1.168.192.in-addr.arpa name = Pi-Hole.

Ok, thanks. Let's double-check your Pi-hole installation.

At the Pi-hole, enter: cat /etc/pihole/install.log

... and let's check for errors: cat /etc/pihole/setupVars.conf

Ok, again not what I initially asked but it reveals some more.

Above bit tells me it appears the Windows client is directly querying the Pi-hole IP address 192.168.1.254 for DNS resolution which is good.
To be sure no other DNS servers are used by the Windows client (and at same time see who is doing DHCP for your network), check below on the Windows client:

C:\Users\deHakkelaar> ipconfig /all | findstr "Server"
   DHCP Server . . . . . . . . . . . : 10.0.0.2
   DNS Servers . . . . . . . . . . . : 10.0.0.2

And when your run below one on the Windows client PC (replacing <WINDOWS_PC_IP_ADDRESS> with the actual IP address of the Windows PC), does it show the correct name now ?

nslookup -type=ptr <WINDOWS_PC_IP_ADDRESS>

After making sure /etc/resolv.conf contains nameserver 127.0.0.1 on Pi-hole, did you reboot Pi-hole to make sure this setting persists/survives a reboot ?
Do names show up now on the web GUI after a reboot ?

1 Like

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.