Top Clients - Only IP's shown?

General Beta 6.0
1

I updated my Pi-hole 5.x to development-v6 yesterday.
Now the dashboard is only showing IP's not DNS names as in 5.x where all DNS names were correctly shown for both Top and Blocked clients.
All client names are visible/readable on DHCP page but not on dashboard...

image
image555×422 5.11 KB

Any setting I should change to make this work again?

Token:
https://tricorder.pi-hole.net/9St1ci41/

Thanks in advance!!

2

Sorry for the delay in replying. Are you using your Pi-hole also as DHCP server?

If so, could you log into your Pi-hole using SSH and run

dig -x 192.168.0.83 @127.0.0.1

What is the output?

3

Hi,
Yes Pi-hole is managing both DHCP and DNS.

Output:

; <<>> DiG 9.18.19-1~deb12u1-Debian <<>> -x 192.168.0.83 @127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24553
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;83.0.168.192.in-addr.arpa. IN PTR

;; ANSWER SECTION:
83.0.168.192.in-addr.arpa. 0 IN PTR Jockes_M10_Plus.groupwork.

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)
;; WHEN: Mon Jan 29 07:08:58 CET 2024
;; MSG SIZE rcvd: 93

(The IP belongs to an old-ish Android tablet)

Note:
Installation is updated from 5.x (latest available ~2 weeks ago) to 6.x dev.

Token:
https://tricorder.pi-hole.net/inQrnq57/

4

This shows that - in theory - local name resolution does work as expected. Also your resolver settings are as default per your debug log. Unfortunately, this means we need to dive a bit deeper, but that won't be a problem.

Please start off with

sudo service pihole-FTL stop
sudo pihole-FTL --config debug.resolver true
sudo rm /var/log/pihole/FTL.log
sudo service pihole-FTL start

After a few minutes, go to /var/log/pihole/FTL.log and check for messages beginning with DEBUG_RESOLVER. Without knowing what is causing the issue, I cannot really say what to look out for but maybe you can simply provide some of those lines here and we can check together. You can also send them to my via a private message if you prefer this for privacy reasons.

5

Thanks a lot for helping!

Log (snip) sent.
Stopped logging with:

sudo service pihole-FTL stop
sudo pihole-FTL --config debug.resolver false
sudo rm /var/log/pihole/FTL.log
sudo service pihole-FTL start

That's enough?

6

Yes. And thanks for the log file.

Interestingly your log shows an issue I thought has been fixed a long time ago, but it appears

https://github.com/pi-hole/FTL/pull/1826

is still in the reviewing process.

Please try running

pihole checkout ftl fix/resolver

and see if this fixes the issue you are seeing.

1 Like
7

Big thanks, issue solved immeditely! :upside_down_face:

1 Like
8

The fix has passed review process and is now included in development-v6. You should go back over there to continue receiving further updates. Thanks for confirming that this PR solved the issue for you. One could only assume that this confirmation is what suddenly made the review process going again :slight_smile:

1 Like