I installed a Pi-hole in a docker container (Docker Tag 2022.07.1, Pi-hole v5.11.4, FTL v5.16.1, Web Interface v5.13
) running on a RPi host (Linux raspberrypi 5.15.32-v8+ #1538 SMP PREEMPT Thu Mar 31 19:40:39 BST 2022 aarch64 GNU/Linux
).
Almost everything works: the DHCP server provides IPs to clients, I can resolve internal names (from DHCP) and external ones both from the Pi-hole and any client.
The one thing that does not work: the resolution of the name of the host (the Rpi) itself. Below is an attempt to resolve a public host, an internal host and the RPi itself from a Windows 10 client that received its IP from Pi-Hole:
PS C:\Users\yop> nslookup
Default Server: pi.hole
Address: 192.168.0.2
> lemonde.fr
Server: pi.hole
Address: 192.168.0.2
Non-authoritative answer:
Name: lemonde.fr
Address: 151.101.2.137
> chromecast.home.arpa
Server: pi.hole
Address: 192.168.0.2
Name: chromecast.home.arpa
Address: 192.168.0.177
> raspberrypi.home.arpa
Server: pi.hole
Address: 192.168.0.2
Name: raspberrypi.home.arpa
Addresses: fe80::909c:4c34:b85e:b6c8
0.0.0.0
> exit
PS C:\Users\yop> ping raspberrypi.home.arpa
Ping request could not find host raspberrypi.home.arpa. Please check the name and try again.
I have updated the name in /etc/hosts
to account for the local domain home.arpa
and did not make any adjustments beyond that:
root@raspberrypi:~# cat /etc/hosts
127.0.0.1 localhost
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
127.0.1.1 raspberrypi.home.arpa
What am I missing?
Having this resolution is quite importnat for me because I have other containers and would like to CNAME their name to raspberrypi.home.arpa
.