Hello,
my Pi-Hole running on DS-lite FTTH has a custom hostname rpi-dnshole since forever. This showed up as server name when doing tests with dig or nslookup.
Recently I see the queries answered by server name pi.hole instead of rpi-dnshole.
Not sure if this is related, but I have seen this the first time after updating to the latest Pi-Hole version since a longer update pause, maybe its a feature I'm unaware of.
I prepared a screenshot with variations of nslookup tests.
- As you can see,
Server:is alwayspi.hole. That section previously always showed my custom hostnamerpi-dnshole. Why is that so?
Another thing that confuses me is, the first two queries are Ok for me since they show my the well known IPv6 and IPv4 of my rpi-dnshole
-
The 3rd query, using
pi.holeas querying server, it shows me one of 2 IPv6 assigned by FritzBox DHCPv6. -
So why is the DHCP assigned IPv6 using
pi.holeas server/hostname and not alsorpi-dnshole?
I see 2 IPv6 DHCP assigned to pi.hole. Is there a simple explanation why pi.hole uses the /64 and not the /128?
To summarize:
Is this all intended behavior or do I have configuration issues somewhere?
-
Should I maybe change hostname to pi.hole with raspi-config to avoid confusion?
-
Not exactly sure how the
pi.holehostname works anyways. It does not show in Fritzbox, there the server is still known asrpi-dnshole -
The current FQDN is
rpi-dnshole.fritz.box. Would a FQDNpi.hole.fritz.boxpossible at all in regard of naming conventions?
A 2nd off-topic which is confusing me, maybe theres a quick answer, else pls ignore.
FritzBox provides IPv4 and IPv6 DHCP, A is OK/IP but AAAA request answer for rpi-dnshole.fritz.box from local network machines result in NODATA. Is that working correctly?
