Pi-Hole IP Ping - Server hostname IPv6 no longer pingable

[mx2k]

So I tried some more pinging my Pi-Hole server with rpi-dnshole hostname. For whatever reason it is no longer pingable under its IPv6 address.

Just to be safe I added the IPv6 to the local DNS settings. See results. ping rpi-dnshole works. ping -6 rpi-dnshole doesn't.

Just to be safe I checked the IP6 of rpi-dnshole. This works.

• Where's my error that ping -6 rpi-dnshole doesn't respond with the servers IP6 fe80::e9dc:8727:cead:f6c8

[jfb]

Ping is not a reliable way to test domain resolution. A better option is to use either nslookup or dig.

From the PC, what is the output of the following from the command prompt?

nslookup rpi-dnshole

Then, in the dnsmasq log at /var/log/pihole.log, what query, reply and forward for this domain are shown?

[mx2k]

Only retruns the IP4, not the IP6.

[jfb]

@jfb

in the dnsmasq log at /var/log/pihole.log , what query, reply and forward for this domain are shown?

Please provide this information.

[mx2k]

This is what I found

Oct  4 21:49:58 dnsmasq[31467]: Pi-hole hostname rpi-dnshole is ::1
Oct  4 21:55:45 dnsmasq[31467]: query[AAAA] rpi-dnshole from 127.0.0.1
Oct  4 21:55:45 dnsmasq[31467]: Pi-hole hostname rpi-dnshole is ::1
Oct  4 21:55:46 dnsmasq[31467]: query[A] rpi-dnshole.fritz.box from fe80::a41f:aed6:1ea7:bbe3
Oct  4 21:55:46 dnsmasq[31467]: forwarded rpi-dnshole.fritz.box to 10.1.1.1
Oct  4 21:55:46 dnsmasq[31467]: reply rpi-dnshole.fritz.box is 10.1.1.6
Oct  4 21:55:46 dnsmasq[31467]: query[AAAA] rpi-dnshole.fritz.box from fe80::a41f:aed6:1ea7:bbe3
Oct  4 21:55:46 dnsmasq[31467]: forwarded rpi-dnshole.fritz.box to 10.1.1.1
Oct  4 21:55:46 dnsmasq[31467]: reply rpi-dnshole.fritz.box is NODATA-IPv6

[jfb]

Please upload a debug log and post just the token URL that is 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

[mx2k]

https://tricorder.pi-hole.net/Rx5uNHDp/

[mx2k]

Made a dig rpi-dnshole on the server itself. think that made no sense and just confirms unbound is working properly.

Also I see a different IPv6 in pihole -d than the one originally determined by pihole -r, which was fe80::e9dc:8727:cead:f6c8

IPV4_ADDRESS=10.1.1.6/8
IPV6_ADDRESS=2a00:6020:[xxxx]:2229:9a27
PIHOLE_DNS_1=127.0.0.1#5335

This is the Pi-Hole IPv6 fe80::e9dc:8727:cead:f6c8 I distribute with DHCPv6 as to the clients as the custom DNS server to use. Now I'm confused by IPV6_ADDRESS=2a00:6020:[xxxx]:2229:9a27.

Which is the one I should use to distribute to clients per DHCPv6?
Afaik the IPV6_ADDRESS=2a00:6020:[xxxx]:2229:9a27 can change over time where as the fe80::e9dc:8727:cead:f6c8 is show static lifetime forever in ip addr

nslookup with rpi-dnshole as server to use. This uses the fe80: static local server IP provided with DHCP.

nslookup with pi.hole as server to use. This uses the IPv6 from setupVars section as shown in pihole -d

My network seems working but since the latest 2-3 major Pi-Hole updates some things seems different and get me confused.

Thanks for all your help in advance.

[mx2k]

Noticed another thing:

when I nslookup pi.hole it shows both IP4 and 6. Only rpi-dnshole has lost his IP6 in query results

Since the latest updates the hostname also changed in dashboard top lists. What now lists as pi.hole was all the time before rpi-dnshole

There is really something fishy going on with my Pi-Hole.
Maybe it makes sense to run pihole -r again?

• pihole -up Update also threw an error while auto updating installed packages because apt update detected kernel update. No other errors or warnings through the update process. Can this be related?

[mx2k]

Then pi.hole exists twice in network table now. The rpi-dnshole hostname is just gone from Pi-Hole logs completely. Still can use it as hotstname for ssh or http access.

[yubiuser]

Did you try setting PIHOLE_PTR=HOSTNAME in pihole-FTL.log and restart pihole?

[mx2k]

Ok lets just say my whole approach was wrong. I never really knew that you not necessarily have to access Pi-Hole with the myself-assigned Raspberry hostname rpi-dnshole.fritz.box

The default configuration just works fine by just using pi.hole for SSH and Admin. Probably did work that way from the beginning, but I just didn't realize.

Interestingly, when using pi.hole for the admin panel instead of rpi-dnshole, the below requests are no longer constantly created while admin panel is open in browser.

Since I can access it under both hostnames, pi.hole and my own, I guess I just wasn't aware the Server can have multiple hostnames/local domain names.

If this assumptions are correct, I guess my problem is fixed. Still not sure what of the big update last month make it change the name displayed in stats.

Thx for help anyways