You are most likely using an IPV6 DNS resolver (IPV6 takes priority over IPV4 when both are set-up).
You can either disable IPV6 in/on your network/client, OR, make sure that your router is broadcasting/using yout IPV6 IP of your Pi-hole as the IPV6 DNS (or manually set it up under your client IPV6 settings).
Yes, that, HOWEVER, you need to make sure that the IPV6 stays the same on the Pi-hole device and does not change (compared to IPV4, IPV6 behaves differently). You can kind-of achieve that with several network related changes on the Pi-hole device OR simply disable IPV6 within the network properties for that adapter under windows …
If IPV6 is desidred, you can then specify the IPV6 DNS under the adapter on your client but you MUST set it up as your IPV6 DNS on your router too.
Give it a spin, see where it lands you like that.
If you really need IPV6 within your network, you’ll have to take the long route of establishing stable IPV6 ip addressee on the Pi-hole device.
This is likely not your problem, but I thought I should throw it out there. Does your new router hand out the same IPs as your old one? For example your old router may have handed out 192.168.1.x while your new router hands out 192.168.0.x. You likely set a static IP on your Raspberry Pi when setting up Pi-Hole using your old router, and switching to the new one could have caused some issues if it doesn’t use the same IP.
Does your new router hand out the same IPs as your old one?
I also had to set static ip on most devices on my network. Lucky some devices had no problem connecting to the network, that is including the pi-hole.
I had a ASUS router that stopped working for some reason. I was able to get the pi hole to work by running it as the DHCP server. With this router I have right now, which is a Linksys AC3200 WRT32X, I want to run it by this forum if I could do the same. In the old router, I was able to disable the DHCP, in this new one, I am not sure if it’s possible.
Here is a screen shot of the DHCP settings on the router:
I don’t believe those are the local DHCP settings. The settings you are trying to change are meant for connecting to the internet, and you should leave it as DHCP (or your internet will not work). What does the “Local Network Settings” tab show? There should be another page somewhere to configure the local DHCP server.
I have disabled the DHCP on my old router and the pi-hole did it’s job. On this new router, I cannot find a way to disable the DHCP so I could use the pi-hole.
After some searching on other forums, I found this entry which the message: From the thread
Workaround to disable DHCP Server function in WRT32X
04-08-2018 01:26 PM
I had the same issue to use WRT32X in bridge mode. Because of the better 5G WIFI support I want to keep the original firmware. Here is my workaround to disable DHCP server function:
1. Reduce the DHCP pool size includes only one IP: start IP 192.168.1.254, end IP 192.168.1.254 (not changeable)
2. Make an IP fix assigment, assign the IP 192.168.1.254 to a MAC adresse, which not exists in your home network.
Works without any issue.
It does, but it’s one nasty way of handling the issue.
It basically reduces the range of dhcp available IPs.
You’d have to make sure the range on the Pi-hole DHCP does not include that IP
What you can do, is to set the IP of the Pi-hole device, either at the begining of that range or at the end, to occupy that one IP …