PiholePi-Hole for custom domain names over LAN DNS
PiholePi-Hole for custom domain names over LAN DNS
Hey, I see you're trying to set up custom hostnames using Pi Hole for your LAN PCs and VMs. You have OpenWrt APs and a few servers, and you're wondering how to do this since Pi Hole works with DNS. You mentioned something like 192.16.0.11 pointing to pc.local, and you want a simple setup that’s easy to understand.
Here’s a quick breakdown:
- You need a way to translate IP addresses into hostnames.
- Pi Hole can help by managing DNS records.
- You can add your custom rules in `/etc/hosts` or configure DNS properly.
- For reliability, consider using a dedicated DNS server or service like Pi-hole itself for better performance.
If you want a straightforward fix, you could edit `/etc/hosts` to map the IPs to names, but be aware it can be tricky and slow. Alternatively, set up a simple DNS entry in Pi Hole that points your VMs to your local network. Let me know if you need step-by-step guidance!
Your device handles IP resolution independently of pinging. At the beginning of the ping sequence, it identifies the IP address, and thereafter it relies on that IP consistently—no further lookups for hostnames occur. To verify this, execute the tests simultaneously in different windows: ping pc.local -t ping 192.168.0.11 -t. You should observe identical packet loss results in both cases. From the pattern you notice, it likely points to either a network loop or an IP conflict involving 192.168.0.11.
I don’t have the exact details, but you could look into checking the network settings or using diagnostic tools to verify connectivity.
Yes, after removing the pihole, you should be able to ping normally again.