Dashboard Displays Hostnames on Pi1 not on Pi2

seh2000 · January 5, 2024, 12:58pm

Hi,
Migrated existing Pi-hole v5 to v6 on Pi1
Here the Dashboard Displays the Hostnames
Created a second instance on a different Pi from scratch
Here the Dashboard don't Display the Hostnames

On both I have created under Local DNS Records a Domain name for the corresponding IP address.
Both Pi1 and Pi2 sits on same router but on separate subnets 192.168.1.0 / 192.168.2.0
On Pi1 the command dig @192.168.1.1 skyq-2 shows:

; <<>> DiG 9.16.44-Debian <<>> @192.168.1.1 skyq-2
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16975
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;skyq-2.                                IN      A
;; ANSWER SECTION:
skyq-2.                 0       IN      A       192.168.1.21
;; Query time: 11 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Fri Jan 05 12:35:37 GMT 2024
;; MSG SIZE  rcvd: 51

While same command on Pi2 dig @192.168.2.1 Echopad misses the Answer part:

; <<>> DiG 9.16.44-Raspbian <<>> @192.168.2.1 Echopad
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 39297
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;Echopad.                       IN      A
;; Query time: 10 msec
;; SERVER: 192.168.2.1#53(192.168.2.1)
;; WHEN: Fri Jan 05 12:39:21 GMT 2024
;; MSG SIZE  rcvd: 36

What have I done wrong or how can I solve?

Bucking_Horn · January 5, 2024, 1:17pm

Check the Query Logs of both your Pi-hole's:
Do the requests register in the expected Pi?

Also, please upload a debug log for each of your Pis and share the two tokens.

Please post just the token URLs as generated after the log is uploaded by running the following command from the Pi-hole host terminal:

pihole -d

or do it through the Web interface:

Tools > Generate Debug Log

seh2000 · January 5, 2024, 3:09pm

Hi there,
Thanks for coming back to me
Checked the Query Longs on both and as far as I can see all hits the right Pi-hole.
I use two different Upstream DNS just to be sure to separate.

Debug Logs:
Pi1
https://tricorder.pi-hole.net/UK0uc0HO/
P2
https://tricorder.pi-hole.net/97PP1cfo/

I did nslookup flurry.com 192.168.2.xxx which returned:
Server: pi.hole
Address: 192.168.2.xxx
Name: flurry.com
Addresses: ::
0.0.0.0
So things looks right...(I think)

Bucking_Horn · January 5, 2024, 3:46pm

Your debug logs look insconspicuous.

Please rerun your dig for the failing name and find and share the corresponding lines from /var/log/pihole/pihole.log.

seh2000 · January 5, 2024, 4:34pm

Hi again,
Think some how it works - now.
The dig command returned "Answer" from both.

Pi1:

 dig @192.168.1.1 skyq-2

; <<>> DiG 9.16.44-Debian <<>> @192.168.1.1 skyq-2
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 12047
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;skyq-2.                                IN      A

;; Query time: 19 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Fri Jan 05 16:17:06 GMT 2024
;; MSG SIZE  rcvd: 35

Pi2:

dig @192.168.2.254 echopad

; <<>> DiG 9.16.44-Raspbian <<>> @192.168.2.254 echopad
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29326
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;echopad.                       IN      A

;; ANSWER SECTION:
echopad.                0       IN      A       192.168.2.20

;; Query time: 0 msec
;; SERVER: 192.168.2.254#53(192.168.2.254)
;; WHEN: Fri Jan 05 16:18:17 GMT 2024
;; MSG SIZE  rcvd: 52

FTL.log is sort of empty as I did a Flush Logs sorry, will post when logs gets populated again, there are entries from before I did the dig command on each Pi.

seh2000 · January 6, 2024, 9:02am

@Bucking_Horn
Good morning, P2 is now displaying the hostname in the dashboard.
I changed P2 from Wi-Fi connection to LAN connection. When I set it up I didn't have a spare switch to use.
Old setup
ONT => Edgerouter 4 Eth1 => Switch A => Pi1 + Lan devices
Eth2 => Unifi-U6 => P2 + Wi-Fi devices
New setup
ONT => Edgerouter 4 Eth1 => Switch A => P1 + Lan devices
Eth2 => Switch B => P1 + Unifi U6 + Wi-Fi devices

When checking the FTL.log the log shows for Pi1:

2024-01-05 17:50:48.820 INFO listening on 192.168.1.252 port 53
2024-01-05 17:50:48.820 INFO listening on eth0(#2): 192.168.1.252 port 53
2024-01-05 17:50:48.821 INFO listening on 127.0.0.1 port 53
2024-01-05 17:50:48.821 INFO listening on lo(#1): 127.0.0.1 port 53
2024-01-05 17:50:48.821 INFO listening on fe80::dfde:8e4c:572f:417%eth0 port 53
2024-01-05 17:50:48.821 INFO listening on eth0(#2): fe80::dfde:8e4c:572f:417%eth0 port 53
2024-01-05 17:50:48.821 INFO listening on ::1 port 53
2024-01-05 17:50:48.821 INFO listening on lo(#1): ::1 port 53
2024-01-05 17:50:48.823 INFO PID of FTL process: 3316
2024-01-05 17:50:48.824 INFO FTL is running as user pihole (UID 999)

The FTL.log for Pi2 shows:

2024-01-05 19:03:29.991 INFO listening on 192.168.2.254 port 53
2024-01-05 19:03:29.991 INFO listening on eth0(#2): 192.168.2.254 port 53
2024-01-05 19:03:29.991 INFO listening on 127.0.0.1 port 53
2024-01-05 19:03:29.991 INFO listening on lo(#1): 127.0.0.1 port 53
2024-01-05 19:03:29.991 INFO listening on fe80::604c:a810:7eed:3e39%eth0 port 53
2024-01-05 19:03:29.991 INFO listening on eth0(#2): fe80::604c:a810:7eed:3e39%eth0 port 53
2024-01-05 19:03:29.991 INFO listening on ::1 port 53
2024-01-05 19:03:29.992 INFO listening on lo(#1): ::1 port 53
2024-01-05 19:03:29.994 INFO PID of FTL process: 578
2024-01-05 19:03:29.994 INFO FTL is running as user pihole (UID 999)

Presume this is OK - or?

FTL.log for Pi1 showed the below error message - to be ignored - or?

2024-01-06 07:00:01.816 ERR SQLite3 message: database is locked in "SELECT name FROM network_addresses WHERE name IS NOT NULL AND ip = ?;" (5)
2024-01-06 07:00:01.816 ERR getNameFromIP("192.168.1.213") - SQL error prepare: database is locked

Many thanks in advance - Steen

Bucking_Horn · January 6, 2024, 7:34pm

According to your logs, your Pi-holes reside at 192.168.1.252 and 192.168.2.254.
Why do you request resolution via 192.168.1.1 here?

It should be easy enough to repopulate it, just by running your dig command again.
We'd just be interested in...

seh2000 · January 7, 2024, 12:57pm

My bad with the 192.168.1.1, didn't think when I did the command nor when posted - my apology!
I have re-run dig at 12:42 on both Pi1 and Pi2, however when I do the following command on both the dig isn't shown.

admin@hanloppi:~ $ dig @192.168.1.252 skyq-2

; <<>> DiG 9.16.44-Debian <<>> @192.168.1.252 skyq-2
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16274
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;skyq-2.                                IN      A

;; ANSWER SECTION:
skyq-2.                 0       IN      A       192.168.1.21

;; Query time: 15 msec
;; SERVER: 192.168.1.252#53(192.168.1.252)
;; WHEN: Sun Jan 07 12:42:24 GMT 2024
;; MSG SIZE  rcvd: 51

sudo cat  /var/log/pihole/FTL.log
admin@hanloppi:~ $ sudo cat /var/log/pihole/FTL.log
2024-01-07 04:41:17.095 [30532/T30545] INFO: Gravity database has been updated, reloading now
2024-01-07 04:41:17.180 [30532/T30545] INFO: Compiled 14 allow and 1 deny regex for 26 clients in 79.8 msec

admin@pihole2:~ $ dig @192.168.2.254 echopad.wi-fi

; <<>> DiG 9.16.44-Raspbian <<>> @192.168.2.254 echopad.wi-fi
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49589
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;echopad.wi-fi.                 IN      A

;; ANSWER SECTION:
echopad.wi-fi.          0       IN      A       192.168.2.20

;; Query time: 9 msec
;; SERVER: 192.168.2.254#53(192.168.2.254)
;; WHEN: Sun Jan 07 12:43:13 GMT 2024
;; MSG SIZE  rcvd: 58

admin@pihole2:~ $ sudo cat /var/log/pihole/FTL.log
2024-01-07 04:55:07.100 [11466/T11479] INFO: Gravity database has been updated, reloading now
2024-01-07 04:55:07.112 [11466/T11479] INFO: Compiled 0 allow and 0 deny regex for 22 clients in 0.9 msec

How do I format to HTML?

Bucking_Horn · January 7, 2024, 4:35pm

That's my bad - you'll find queries logged in pihole.log, of course.
I've corrected my post above accordingly.

Apparently, both your most recent dig return correct results.
Is your issue solved then?

Sorry, I do not understand that question.
Where do you want to format HTML?
How is that related to your issue of local names not resolving?

rdwebdesign · January 7, 2024, 6:22pm

I think you were asking how to format your code blocks here on Discourse, right?
(but apparently you already found it)

If your HTML question is related to something else, please give us more details.

seh2000 · January 8, 2024, 10:28am

Hi @Bucking_Horn,
For now I say all appears correct.
I have noticed a small issue, but will check better first, before raising any question.

For the HTML, my bad I should have made my question more clear.
It was/is related to how to format postings here in HTML format, I noticed you did something and the post became more easy to read/understand.

Warm regards - Steen

seh2000 · January 8, 2024, 10:30am

Hi,
Sorry my bad I should have been more clear in my question.
It was/is related to how to format the text in my postings in HTML - I didn't do believe it was Bucking_Horn who did.
So how on format the code blocks?
Warm regards - Steen

Bucking_Horn · January 8, 2024, 11:05am

Aye, that can be achieved by using </> Preformatted text on a selected code block from the editor window's menu, or by pressing Ctrl+e.

seh2000 · January 8, 2024, 11:37am

Thanks!!
Have made a mental note for next time