Pi-Hole not working with Bell 1000 router

[MrStyles]

Hardware:
Computer for Pi-Hole: An old Dell Inspiron 2650
O/S: Lubuntu 18.04
Static IP: 192.168.2.97
Gateway: 192.168.2.1

Network Router: Bell 1000 Router/modem (Sagemcom)
Router IP: 192.168.2.1
DNS Settings:
Primary: 192.168.2.97
Secondary: 192.168.2.97
Domain name is not designated.

Browser error: Page not accessible
additional information from browser: DNS not set up correctly

Results: Can not access any internet web page. All local hardware is accessible by IP address.

If I change the router DNS settings back to Open DNS's servers, everything works again, but of course... no filtering.

If I manually address the Pi-Hole machine in a computer's DNS settings, it works fine.

Does anyone know how to fix this situation? I wanted for all machines to be filtered without having to set them all up manually - this is being used in a Motel, so it would be impossible to set every guest's machine manually.

[jfb]

Please send us the token generated by

pihole -d

or do it through the Web interface:

How do I debug my Pi-hole installation?

Method 1: Generate a debug token via the Web interface Log in to your Pi-hole's Web interface Navigate to Tools > Generate debug log Click the Generate debug log button Send us the debug token [debug] Method 2: Use the command line to generate a debug token Login into your Pi-hole's command line Enter pihole -d Provide us with the debug token that is generated after the debug script completes Alternative: Securely sending us additional information Preferred Method If there is additi…

[MrStyles]

If I try it again at the Motel, we might have a guest revolt (pitch forks and torches) I've requested permission from the manager. Meanwhile, I have the same model modem here at my house, I will try and re-create the issue here.

Yup, does the same at my house... I will try the debug.

[MrStyles]

According to the log, Pi-Hole keeps reverting the gateway back to 192.168.0.1 instead of 192.168.2.1. I've changed this several times and it keeps coming back. Even after a pihole -r reconfigure.

[DanSchaper]

What addresses are set in /etc/dhcpcd.conf for the interface?

[MrStyles]

@DanSchaper

/etc/dhcpcd.conf

it has two sections with the same name, one has the old settings when I did my trial run here at home, and the other with the Motel settings

interface enp2s1
        static ip_address=192.168.0.97/24
        static routers=192.168.0.1
        static domain_name_servers=127.0.0.1
interface enp2s1
        static ip_address=192.168.2.97/24
        static routers=192.168.2.1
        static domain_name_servers=127.0.0.1

I just tried changing those values to the correct ones. I re-booted, and the network status looks correct, but still no go. I've also lost my touchpad functionality again (stupid bug in Lubuntu) I need to re-install the drivers again.

[DanSchaper]

Just remove the extra section that you don't need. There can only be one section in that file.

[MrStyles]

Here is the token: Your debug token is: https://tricorder.pi-hole.net/sofyn71n4k!

Note: I have to keep changing my DNS on my router back to a web DNS in order to post on this page.

[MrStyles]

I've just sent a support question to Sagemcom to see if there is something in the router to change.

[jfb]

Your Pi-Hole debug log doesn't show any problems. It can resolve DNS queries and communicate with the router.

[MrStyles]

Frustrating, because nothing on the network can access the internet as soon as I change the DNS settings in the router. I will try changing it again and power cycle everything on the network including the modem.

[jfb]

Try this to help your troubleshooting - instead of putting the entire network DNS on Pi-Hole, work with a single client with a manual DNS assignment to Pi-Hole. When you get that client working with Pi-Hole DNS, then expand the DNS to your router/network.

[MrStyles]

Power cycle didn't work...

Setting the DNS in my computer works fine...

[MrStyles]

@jfb

When you get that client working with Pi-Hole DNS, then expand the DNS to your router/network.

I'm suspecting that they have built into the router that if a DNS address points internally, that it is either invalid, or it is searching an external source using that address and does not query internally.

Because I can access the internet through the Pi-Hole, but not through the router when I change the DNS to point to the Pi-Hole.

[DanSchaper]

Look for something called either Rebind Protection or DNS Rebind. That will block DNS traffic from an internal address.

[MrStyles]

I don't see any visible options for Rebind Protection or DNS Rebind. They probably didn't allow for that feature to be customized.

[jfb]

You have established that the problem is not with the Pi-Hole. Have you considered getting another router to piggyback on your existing modem/router? You could put the existing router in bridge mode and let the new router do the routing.

[MrStyles]

Unfortunately I don't know if management will go for another purchase at the moment... (we updated the 24 port switches recently). I've e-mailed the manufacturer to see if they can offer a solution to fix the issue. Maybe an alternative firmware.

In the meantime, I'm going to check the "junk pile" for a working router... they grabbed some equipment from another motel that was being torn down.