It doesn't block ads

[MatStef132]

Expected Behaviour:

Block ads

Actual Behaviour:

Doesn't block ads

Debug Token:

5zxps6o4cw

[mibere]

Maybe one of the following FAQs helps?

How do I use Pi-hole's built in DHCP server (and why would I want to)?

Using Your Existing Router For Network-wide Ad Blocking You might not need to use Pi-hole's DHCP server: In many home environments, your router also functions as your DHCP server. In this case, you can often set Pi-hole to be the DNS server for your network clients in the router's DHCP (or LAN) settings page, which allows all of your network clients to block ads simply by connecting to the network. Setting it up this way is also what makes Pi-hole very powerful for network-wide ad blocking. …

Why should Pi-hole be my only DNS server?

Reduced Ad Blocking Capability The main reason you should Pi-hole as your only DNS server is that you will see increased performance in the blocking of ads. If you have two DNS servers (Pi-hole and something else), your network clients may not always query Pi-hole for name resolution. If a query happens to be answered from a non-Pi-hole DNS server, your block lists will not apply (since that DNS server doesn't know about them). All Queries Need To Go Through Pi-hole First Since other DNS se…

What can I do if I can't change manually set the DNS server on my router?

Some routers--often ones provided by your ISP--will not let you set a DNS server for your devices. You can still get use of network-wide ad blocking with Pi-hole. The solution is to disable DHCP on your router and use Pi-hole's built in DHCP server. This usually requires you to disable DHCP on your router. But some models don't even let you do this. The solution then, is to go into the DHCP settings of the router and see if you can limit its address range. By letting it serve only one IP…

[jfb]

Your debug log shows several problems

There does not appear to be an IP address assigned to the Pi and no clients are able to connect to this address for DNS.

*** [ DIAGNOSING ]: Networking
[✗] No IPv4 address(es) found on the eth0 interface.

[✗] No IPv6 address(es) found on the eth0 interface.

[i] Default IPv4 gateway: 192.168.1.1
   * Pinging 192.168.1.1...
[✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)

You have Pi-Hole configured to listen on this address, but that does not appear to be the IP address of the Pi:

*** [ DIAGNOSING ]: Setup variables
...
PIHOLE_INTERFACE=eth0
IPV4_ADDRESS=192.168.1.7/24