PiHole Help
PiHole Help
I've been configuring Pi Hole on a Raspberry Pi 3 and following the guide. However, when connecting my device, the startup process mentions an IP address format of "192.168..." followed by an IPv6 address, while my router uses a different format—like 10.0.0.1. In Pihole it lists 10.0.0.254 as the local IP, but in Rasbian Linux it shows 192.168. The dashboard fails to load and DNS settings don't work. I've already adjusted the static IP in the article, but I need further guidance. Any suggestions would be greatly appreciated!
Did you store dhcpcd.conf and restart the RPi so updates applied? What format does your dhcpcd.conf use concerning static IPs? Why are you choosing this as your DNS server? Do you have a configuration at 10.0.0.254? I assumed this was the local IP you intended for the RPi. When I configured PiHole, I opted for a different method to assign a fixed IP: in my router, I listed connected devices and assigned the RPi’s MAC address to a static IP. Thus even if the RPi uses DHCP, the router consistently provides the same static address along with the DNS/gateway settings. From my perspective, relocating the RPi to another network won’t require altering any configuration files to restore normal operation.
I attempted it. Check the image provided. Do you need to configure the DNS server with the RPI's IP? I changed it to the local address (10.0.0.254) as suggested in the Pi-Hole setup. Also, I can't connect via SSH at the moment. Finding the MAC address seems tricky—seems the router isn't recognizing the hostname. Updated October 29, 2020 by TinsellyCone241
I understand your request. After setting up PiHole, update your router's DNS settings. The "headless" configuration operates via SSH, so you need to add an empty, extension-free SSH file right after creating the SD card in the boot directory. Check the router's web interface for a status section showing the DHCP table of all connected devices.
I'm trying to locate the MAC address for the PiHole since the hostname isn't displaying correctly in the router's web interface. I'm not sure if I should use SSH or not, but it could assist in troubleshooting.