I have normally set up the Pi-Hole nevertheless it seems not to work.
I have changed the Primary DNS through the web Interface.
I use TP-Link Archer VR600.
Actually there is an emulator of the web interface to help you understand better the steps I did. https://www.tp-link.com/resources/simulator/VR600_Emulator/index.htm
I went to Network-> LAN Settings-> Primary DNS (there I inserted the Pi-Hole ip address)
Is that correct? Do I need anything else since it doesnt seem to work for me.
Have you verified that the Pi-Hole works from it’s host device? Assume you have it installed on a Pi, then ssh into the Pi linux terminal and run a few test DNS lookups. If the Pi-Hole is working, the commands below should return a blocked IP for the first command and a valid IP for the second command.
dig flurry.com @184.108.40.206
What is the IP address of your router, and the static IP that you have assigned to the Pi-Hole?
Have you tested Pi-Hole by manually assigning it’s IP address as DNS server on a client? This would point that client directly to the Pi-Hole, bypassing any router DNS.
What do you have for secondary DNS on your router? It should either be blank or the IP address of the Pi-Hole (entered the same as in primary DNS).
Are you using IPV6? If so, what are your IPV6 DNS settings?
The “dig” command from the Linux terminal command line does this.
The purpose of a static IP is so that the Pi-Hole will always have the same IP address, then the router and/or clients can be mapped to a DNS address that doest’t change. In your router, you would find whatever IP address is used for the Pi-Hole now, and make that static (or reserved, depending on your router).
That should work as well.
It’s probably best if you upload your debug log and post the token here. Then we can look at your configuration and see if there is an evident problem.
I found that the FTL engine is not installed…
I saw that the solution is that > edit /etc/resolv.conf and change from 127.0.0.1 to let’s say google’s 220.127.116.11 run a pihole -r and repair.
but i dont understand what I should do.
Quick note : It’s better to fill in the Pi-Hole IP 2 times instead of leaving the secondary DNS IP empty if possible, because some routers then send the secondary WAN DNS server IP to all your clients… VERY annoying!
I have entered the the IP to both Primary and Secondary DNS in the router.
My devices are pretty much the same and that means that Pi has the same IP all the time. Nevertheless if needed to be done I will do it. (I have made the setup numerouns times to figure out what Im doing wrong and the PI always get the same IP.