Raspberry Pi running Pi-hole not blocking ads, unable to ping default gateway

[hobojo]

Please follow the below template, it will help us to help you!

Expected Behaviour:

Pihole is running on my RPi. It should be blocking ads and acting as a DNS for my network devices.

Actual Behaviour:

Pi-hole is not blocking ads. It isn't working as a DNS for my devices. When explicitly setting it as the DNS ip address, my devices (laptop, iphone, etc) can't resolve any website.

My Pi itself is not able to ping my router or any domain (tried 8.8.8.8, etc).

When completely removing pi-hole my raspberry pi connects to the router, web, etc.

Debug Token:

Can't upload my log bue to aforementioned network issue.

debug log removed by moderator

[jfb]

Your Pi-hole is working correctly in that it can block domains on the various interfaces. However, something is preventing Pi-hole from accessing external DNS services.

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] raw.ns.europe.machinevisinet.machinevision.net.zooplus.it is 0.0.0.0e on lo (127.0.0.1)
[✓] raw.ns.europe.machinevisinet.machinevision.net.zooplus.it is 0.0.0.0e on eth0 (192.168.0.116)
[✓] No IPv4 address available on wlan0
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (8.8.8.8)

Are you running any firewall or other software on your network that will interfere with this traffic?

Also, your DHCP server is passing its own IP for DNS, and not the IP of Pi-hole:

*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
   Scanning all your interfaces for DHCP servers
   Timeout: 10 seconds
   
   * Received 548 bytes from eth0:192.168.0.1
     Offered IP address: 192.168.0.116
     Server IP address: N/A
     Relay-agent IP address: N/A
     BOOTP server: (empty)
     BOOTP file: (empty)
     DHCP options:
      Message type: DHCPOFFER (2)
      server-identifier: 192.168.0.1
      lease-time: Infinite
      netmask: 255.255.255.0
      router: 192.168.0.1
      dns-server: 192.168.0.1
      --- end of options ---
    
   DHCP packets received on interface eth0: 1
   DHCP packets received on interface wlan0: 0
   DHCP packets received on interface lo: 0

[hobojo]

No firewall that I know of -- all traffic not going through pihole on my network works fine, including my rpi if i uninstall pihole and revert the dns settings on my router.

this is how my dns is configured on my router (D-Link DIR-880L):

[Bucking_Horn]

Run from a client(!), what's the output of the following commands:

nslookup pi.hole

nslookup flurry.com 192.168.0.116

[hobojo]

nslookup pi.hole
Server:		192.168.0.116
Address:	192.168.0.116#53

Name:	pi.hole
Address: 192.168.0.116

nslookup flurry.com 192.168.0.116

Server:		192.168.0.116
Address:	192.168.0.116#53

Non-authoritative answer:
Name:	flurry.com
Address: 212.82.100.150
Name:	flurry.com
Address: 74.6.136.150
Name:	flurry.com
Address: 98.136.103.23

[hobojo]

bump

any thoughts?

[hobojo]

Anyone able to help?

[yubiuser]

The two outputs show that your client is using Pi-hole as DNS server, but is not blocking a known ad-domain. Are you running some kind of Malware protection software on the client, e.g. AVAST Real site?

[vasundhar]

did you map the gateway ip ( ip of your router) correctly ?
connect to your pi, do traceroute 8.8.8.8 and see if it is routed right

[hobojo]

pi@raspberrypi:~ $ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

[jfb]

This indicates a problem outside of Pi-hole. The route to an IP address is independent of any Pi-hole activity.

[hobojo]

the only thing that solved it was changing my router's DNS configuration away from my raspberry pi's ip address. but i need the DNS to be set to pi's ip address in order to run pi-hole on my network. any thoughts?