Comp missing from top client list (total)

The client can't resolve "pi.hole" and this address is mapped by the Pi-Hole working as DNS server. If you test this from another connected client, do you get the IP address of the Pi-Hole?

What is the IP address of the missing client?

192.168.5.10 is my comp (client) which is missing.
192.168.5.113 is Orange PI zero address
192.168.5.50 is my wife comp
192.168.5.55 should be pi.hole

The Pi-Hole appears to be using the 113 address as well. From your debug log:

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
   192.168.5.113/24 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)
   192.168.5.55/24 matches the IP found in /etc/pihole/setupVars.con

What physical or virtual platform is hosting the Pi-Hole software?

Orange Pi zero
Armbian_5.65_Orangepizero_Ubuntu_bionic_next_4.14.78

I changed IP address from original Armbian to different, to not be confused which is which. I have a crash of pi.hole and still don't know the reason.

The Pi-Hole should be listening on the assigned IP address of the ethernet port (which appears to be the active connection).

Ensure that the IP address assigned to the Zero is static or reserved at the router. Then run pihole -r and select reconfigure; then select the assigned IP address when asked.

I know that, now pi.hole have static address and in router is reserved for pi.hole.
It was always the case, static and reserved.
Now is this

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
192.169.5.55/24 does not match the IP found in /etc/pihole/setupVars.conf (Use IPv6 ULA addresses for Pi-hole)
192.168.5.55/24 matches the IP found in /etc/pihole/setupVars.conf

There may be an error in the first IP address. The rest of your network is on 192.168.xxx and that address is 192.169.xxx.

Do you know how to change that typo?

Confirm the IP configuration on the Pi with ip addr

You can look in /etc/pihole/setupVars.conf and see if that line appears. If so, delete it.

No its not there only this
IPV4_ADDRESS=192.168.5.55/24
Thanks man for your patience with newbie like me,

Let's look for the missing client.

On the terminal on the Pi, run this command to live tail the pihole.log, and leave the window open:

tail -f /var/log/pihole.log

Then, on the missing client, open a browser and open www.cnn.com. This should result in a burst of activity in the pihole log from that client, starting with some cnn domains.

No there is no activity. just 15 lines of text

Dec 3 20:53:49 dnsmasq[1216]: 2341 192.168.5.50/53658 reply block-debug.x.dropbox.com is 52.6.78.241
Dec 3 20:53:49 dnsmasq[1216]: 2341 192.168.5.50/53658 reply block-debug.x.dropbox.com is 52.7.182.237
Dec 3 20:53:49 dnsmasq[1216]: 2341 192.168.5.50/53658 reply block-debug.x.dropbox.com is 52.21.155.87
Dec 3 20:53:49 dnsmasq[1216]: 2341 192.168.5.50/53658 reply block-debug.x.dropbox.com is 52.73.220.123
Dec 3 21:09:10 dnsmasq[1216]: 2342 192.168.5.50/53300 query[A] d.dropbox.com from 192.168.5.50
Dec 3 21:09:10 dnsmasq[1216]: 2342 192.168.5.50/53300 forwarded d.dropbox.com to 1.0.0.1
Dec 3 21:09:10 dnsmasq[1216]: 2342 192.168.5.50/53300 forwarded d.dropbox.com to 1.1.1.1
Dec 3 21:09:10 dnsmasq[1216]: 2342 192.168.5.50/53300 reply d.dropbox.com is
Dec 3 21:09:10 dnsmasq[1216]: 2342 192.168.5.50/53300 reply d.v.dropbox.com is
Dec 3 21:09:10 dnsmasq[1216]: 2342 192.168.5.50/53300 reply d-sjc.v.dropbox.com is 162.125.34.137
Dec 3 21:21:43 dnsmasq[1216]: 2343 192.168.5.50/55052 query[A] bolt.dropbox.com from 192.168.5.50
Dec 3 21:21:43 dnsmasq[1216]: 2343 192.168.5.50/55052 forwarded bolt.dropbox.com to 1.0.0.1
Dec 3 21:21:43 dnsmasq[1216]: 2343 192.168.5.50/55052 forwarded bolt.dropbox.com to 1.1.1.1
Dec 3 21:21:43 dnsmasq[1216]: 2343 192.168.5.50/55052 reply bolt.dropbox.com is
Dec 3 21:21:43 dnsmasq[1216]: 2343 192.168.5.50/55052 reply bolt.v.dropbox.com is 162.125.18.133

On the missing client (Linux based) open up a terminal window and see what nameserver it is using:

cat /etc/resolv.conf

nameserver 127.0.2.1

Change that to the IP of the Pi-Hole (192.168.5.55)

How? It say

 Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
     **DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN**

You would edit it with sudo nano /etc/resolv.conf

This will change it for now, and I'm not sure what may change it back later.

I don't know your configuration on that Linux distribution on that client. You can look through the network setting options on that client (I assume it has a GUI desktop interface) and see what software changes it.

I changed in terminal. This address show in pi.hole as local host, but with very low traffic. Just 35 requests. Lat see whats happens now. Let see cnn.com
YESSSSSSSSS. this is it .Thank you very, very much. Good Night.
I don't know where you now.

After a good sleep, lets recapitulate :slight_smile: First big thanks to moderator
@jfb for walking me patiently. Now resolve

This is not pi.hole problem instead it's problem of client OS Linux Mint 18.3 and upstream to Ubuntu and systemD
To resolve this it's necessary to edit on client computer
/etc/resolvconf/resolv.conf.d/tail and write
"nameserver <pi.hole IP address>"
Save and restart and you will have pi.hole listed in /etc/resolv.conf witch is normay overwritten on computer restart. Now pi.hole is listing my comp in client list
Thank you again. Yoss

1 Like

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