The issue I am facing:
Hello there! I've been using Pi-hole for quite a while now, but today we had an upgrade on our internet connection which required the change of the router. And because of some other reasons I decided to make a brand new Pi-hole install.
Made the changes on the router to assign a static IP, but it looks like either the router refuses to use Pi-hole as a DNS server, or Pi-hole isn't connecting/working as expected. I can assign a primary and a secondary custom DNS server on the router, and it doesn't work when I only assign Pi-hole IP (192.168.1.254). For now I have assigned Google DNS - 8.8.8.8 - as secondary DNS in order to be able to connect to anything, because otherwise computers/smartphones are unable to reach any outside address.
Details about my system:
Pi-hole is running on a Raspberry Pi 512MB (yep, it's an old one), router is a Sagemcom f@st 5670. I couldn't find any information about this one on the internet other than a press release from Sagemcom, not even an user manual. I may be wrong but it looks like it was custom-designed for TIM Telecom Brazil. The Pi is connected to the network through wi-fi with an USB dongle that works just fine, as I'm able to SSH into the Pi without problems.
What I have changed since installing Pi-hole:
It's a brand new Pi-hole install, other than the changes on the router everything is the same as the previous install, which worked just fine.
Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:
And reading the log now it looks like the DNS started to be seen by the Pi itself, but not the other machines on the network. Maybe a propagation issue? (I may be talking nonsense, it has been a long time since I was into network administration)
Looks like the router's interface is almost similar to mine. Unfortunately the menu is slightly different, on mine there isn't a DNS option on that part of the configuration, just DHCP. And indeed the only place where I can change the DNS server is in the WAN configuration.
Looks like this new router is one of those, which is a bummer. I will setup a custom OPNsense router to solve that, the idea being using the OPNsense machine to deal with my home network (including wi-fi access to smartphones and laptops), setting up the Pi-hole machine as the DNS server, and then connect it to the internet provider router for internet access. Let's hope that will work.