Ok so that is working as intended. Last step is to point the lan side dns to the piholes ip. I couldn't find a good document on your router but it should be in a lan section or maybe a dhcp tab. Not sure if your router will reboot on that change or not. If it doesn't you'll need to reboot the clients to get the updated DNS setting. Hopefully this works for you.
As soon as I point my router to use my pi hole it disconnects the internet. I restart the router and same thing again, no internet.
I put the DNS addresses back to 1.1.1.1 and 9.9.9.9 and it reconnects.
Ok so we know its something router related. Can you share a screen shot of the page where the changes are being made in the router?
Scratch that for a moment. I just noticed that your changing this on the WAN setting page. What does the DHCP tab show?
Note that the WAN setting is for your router itself. It is the address it uses to resolve things like NTP clocks. It can be what you currently have it set as. Your looking for LAN setting or DHCP settings.
No worries. Under the DHCP tab that you showed is there anything below that area that says "customer option 1" looking for anything dns related.
Also, a few tabs over from the "LAN" tab there is a Manual DNS tab. Is that the same tab as the WAN tab you first posted?
Added comments:
I did some searching on the web with little help. The online manuals I've found are really simple setup manuals and don't have info about advanced setups.
Reddit had little info. I found this post from several months ago that went unanswered. Seems like your same issue.
Is anyone familiar with setting up a Pihole on their fast 5290?
I have set up a Pihole on my local network and when I try to configure my router DNS settings it cannot establish a connection. I've tried configuring my DHCP server a few different ways as well, but I don't think I'm doing it right. I've tried manual DNS on 8.8.8.8 and it works, but when I change it to my Pihole it doesn't work. I can manually configure DNS on individual devices with the Pihole and it works, but I'm wanting to use it for a couple of fire sticks which do not have manual DNS settings. Would anyone be able to give me some direction with this specific router? If I can't figure it out, I plan to get my own router, but I would like to get this up until then.
If all else fails your can turn off your DHCP on your router and use the Pihole as the DHCP Server as well as DNS. This guide has some info on that.
Hopefully you can find the option in the router but its not something you can change.
For your question under the DHCP tab those two pictures are what I get only unfortunately. The only thing I left out was a section for reserving IP addresses.
This is what is under the Manual DNS tab:
As you can see I already put the pi hole's ip address there but it does nothing.
I'll try using the pi hole provided DHCP and DNS and I'll get back to you.
I wanted to include this as well:
Whatever you had me do has fixed my pi hole. I routed my phone to use the pi hole's ip address as the DNS server and it is working whereas before it wasn't. So thank you for fixing my pi hole, at least as far as it is working like it's supposed to with something pointed to it specifically.
Finally here is my debug token:
https://tricorder.pi-hole.net/pRDhcKSd/
I am now using my pi hole as the DHCP server and all seems to be doing well. I will wait a couple days for all the old leases from my router release and for them to pop up on the pi hole. Once that happens I will come back and let you know how everything is working.
As for right now, it is working like it's supposed to.
1 Like
You don't need to wait.
You can force each device to renew the leases.
Usually turning the device network interface down and up again will force the renew.
I know I don’t and I can force the release, but this gives me an opportunity to see if any new problems arise during the night. Right now everything is working as it should which is a stark contrast to when I tried to use my pi hole as a DHCP server before and nothing worked.
Edited to add:
Everything works like it should when other clients are getting an ip address from thr pihole. But when the pihole dropped off the lease from the router it never got one from itself and I lose internet connectivity.
One way to solve this is to run two dhcp servers.
Turn DHCP back on for the Router - for simplicity, change the router to 192.168.254.1 ( from 192.168.254.254 ) and give it a starting range of 2 and ending range of 2 9 Or 192.168.254.2 to 192.168.254.2 if it needs ips ).
Set the pihole static IP to 192.168.254.2.
On the Pihole leave DHCP on but change its range to 192.168.254.3 to 192.168.254.254. Make sure to point to update the routers ip in the DHCP setting.
This will allow the Pihole to get its IP from the router but only the pihole.
You may be able to keep the routers IP at 254 and use a starting ip of 253 and then assign the ip to that 253 ip. The idea is to have a small range for the router that only serves the pihole and have the pihole serve the rest.
I figured I might have to do that and let the router just handle the pihole so I started working on the shortly before you replied to my edited comment.
As of right now everything is working off the pihole's DHCP server and the router is only handling the pihole.
Thanks again for your help (and everyone who added comments to help out), I'm not sure what you had me to do get my pihole to work but you got it working in regards to what it was doing before with the networking issues.
Not sure. It very well may have been a combination of things ( faulty SD card, some setting, maybe the pi itself is starting to go etc). Glad its working for you though.
1 Like
I was suspecting my pi hole was getting defective so I actually ordered another one as backup just in case, but for now its still in the wrapper it came in until this pi finally lets go.
With that being said, I'm not sure which comment to mark as the solution.
Your pi / networking certainly complicated it but ultimately its changing your DHCP settings as your router doesn't allow for changing lan side DNS. It would have been an issue no matter what.
I'm glad you (and everyone else) helped me solve it, thank you.
I'm sure maybe a faulty sd card or my reader being faulty before was complicating things but I'm glad its all done now. I'll make the comment you posted about turning my pi as the DHCP as the solution.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.