Issue with the Pi hole functionality.
Issue with the Pi hole functionality.
You configured the pi hole successfully, but your ISP router doesn’t support a new work wide DNS. Since you’ve used a static IP and followed the forum instructions, the pi hole should be reachable. When setting up your phone (S9) to connect, it shows “no internet.” You adjusted the DNS in advanced settings to point to the pi hole’s IP, but the issue persists. Did you configure anything else or check the router’s status?
You configured your DNS settings in Pi Hole, but using your ISP servers caused issues. Switching to Google's DNS resolved the problem. On your tablet, you need to toggle WiFi on and off for Pi Hole to function properly. Changing the DNS sometimes triggers temporary connectivity glitches.
I can reach the Pihole UI via the browser. The entire network becomes an issue because the ISP's router doesn't offer all features.
In the settings, DNS is active with both Google and Cloudflare included.
On your device configure the DNS server with your Pi's IP address, then confirm. After it confirms connection, turn off your Wi-Fi for a short time, wait a moment, then turn it back on. It should restore properly.
You'd still rely on your router as the main gateway, and clients would recognize it as such. The problem arises when a device loses connection; it wouldn't be able to obtain a valid IP address unless you enable the Pi-hole or configure it statically. Even if the Pi-hole fails, your network remains reachable as long as you assign a secondary DNS (your ISP's DNS) to all clients. I've implemented this at the router level—using the primary DNS as the Pi-hole and a backup DNS in case the Pi-hole goes down, allowing the network to switch seamlessly.
You'll find the standard DNS resolution for google.com using pi-hole. Run the command on the Pi-hole Linux setup to observe the results directly.