Please follow the below template, it will help us to help you!
Expected Behaviour:
Pi-hole is blocking ads across all devices connected to the router
Actual Behaviour:
Pi-hole is connected to the internet, but opening browser results in DNS_PROBE_FINISHED_BAD_CONFIG
For the longest time I have not been able to get my pihole to work.
Let me give you some background: early on, if the DNS was specified manually on the router to have only the IP address of the Pi, no device could connect to the internet. I tried updating the pi and pinging 8.8.8.8 but would result in 100% packet loss. What I found when I typed in sudo route -n
was that none of the gateways pointed to the IP address of the router. I then forced it onto the list by typing in sudo route add default gateway 192.168.x.x
and now the pi could ping 8.8.8.8 and the pi was updated. However, this did not fix the problem and when connecting to the internet via the browser get a DNS_PROBE_FINISHED_BAD_CONFIG.
For reference, I tried following the instructions on this page but did not help me solve the issue Pi-Hole works on Pi, returns DNS_Probe_Finished_Bad_Config on desktop
My apologies if this is a repost but a search so far has found me no results that have fixed my issue. I am certain it is a configuration problem, if relevant, the devices used to connect to the internet are:
Windows 10 Chrome Browser
Android Chrome Browser
Sagemcom Fast 5260 is the router used
Debug Token:
piljedwih8