Pi Hole not matching IP and not able to ads block (lack of network knowledge)

locnguyen · January 1, 2020, 3:39am

Expected Behaviour:

Reimage raspberry pi (personal annoyance)
look at what static IP is and find which one I could assign to PiHole static IP (within the range provided by DCHP). My range is 192.168.100-192.168.199. I picked192.168.0.190
Installed PiHole and used the static IP during setup from step 2 (192.168.0.190)
Added the IP from raspberry pi to Reserve IP Address DHCP in my router then reboot (192.168.0.111)
then add IP DNS( generated by pi hole installation) to my router then reboot (192.168.0.190)

I expected it to be able to block ads just like that I guess not..

Actual Behaviour:

It's just not able to block ads even though pihole detects it on the network.

Debug Token:

https://tricorder.pi-hole.net/r8zjbqmpy2

Tesserax · January 1, 2020, 4:20am

@locnguyen The issue I see right away is the DNS settings in your router. You should have a single address of the Pi-hole there. No other addresses should be used. Once done, your Mac should only see the Pi-hole DNS address of 192.168.1.190.

locnguyen · January 1, 2020, 4:26am

@Tesserax Thanks for the tip! I am not sure how to remove the other ones. I actually cant remove it. within the settings. I want to make sure that this is a network wide appliance.

I've assigned 8.8.8.8 as a secondary DNS.

I've also seen people set up wireless LAN

Do you have any recommendations?

Tesserax · January 1, 2020, 4:31am

@locnguyen Remove 8.8.8.8 from your router's settings. You should only have the Primary DNS set to: 192.168.1.190

Also let's check the status of your Pi-hole service. To do so, start an SSH session to your Raspberry Pi. Then at the prompt, enter: pihole status

A fully functional Pi-hole should report back with green check marks for both "DNS service is running" and "Pi-hole blocking is enabled."

jfb · January 1, 2020, 4:31am

In addition to the un-needed second DNS of Google (8.8.8.8), what have you set up for your gateway when you set up Pi-Hole? Your debug log shows Pi-Hole trying to find a gateway at IP 189, and this does not appear to be the actual gateway IP (the IP of the router).

[i] Default IPv4 gateway: 192.168.0.189
192.168.0.10
   * Pinging 192.168.0.189
192.168.0.10...
[✗] Gateway did not respond.

Your gravity list is also empty - this is the master list of domains to block. With this list empty, nothing will be blocked. This is why the "domains on blocklist" on your dashboard shows zero. Fix this by updating gravity via the command line with pihole -g or via the web admin interface.

locnguyen · January 1, 2020, 4:48am

@Tesserax I've removed the 8.8.8.8 yet it still doesnt work

pi@raspberrypi:~ $ pihole status
  [✓] DNS service is running
  [✓] Pi-hole blocking is Enabled

The Other two still shows up

@jfb do you know where I could fix that? I set it when I did pihole -r


pi@raspberrypi:~ $ pihole -g
  [i] Pi-hole blocking is enabled
  [i] Neutrino emissions detected...
  [✓] Pulling blocklist source list into range

  [i] Target: raw.githubusercontent.com (hosts)
  [✗] Status: Connection Refused
  [✗] List download failed: no cached list available

  [i] Target: mirror1.malwaredomains.com (justdomains)
  [✗] Status: Connection Refused
  [✗] List download failed: no cached list available

  [i] Target: sysctl.org (hosts)
  [✗] Status: Connection Refused
  [✗] List download failed: no cached list available

  [i] Target: s3.amazonaws.com (simple_tracking.txt)
  [✗] Status: Connection Refused
  [✗] List download failed: no cached list available

  [i] Target: s3.amazonaws.com (simple_ad.txt)
  [✗] Status: Connection Refused
  [✗] List download failed: no cached list available

  [i] Target: hosts-file.net (ad_servers.txt)
  [✗] Status: Connection Refused
  [✗] List download failed: no cached list available

  [✓] Consolidating blocklists
  [✓] Extracting domains from blocklists
  [i] Number of domains being pulled in by gravity: 0
  [✓] Removing duplicate domains
  [i] Number of unique domains trapped in the Event Horizon: 0
  [i] Number of whitelisted domains: 1
  [i] Number of blacklisted domains: 0
  [i] Number of regex filters: 0
  [✓] Parsing domains into hosts format
  [✓] Cleaning up stray matter

  [✓] Force-reloading DNS service
  [✓] DNS service is running
  [✓] Pi-hole blocking is Enabled

technicalpyro · January 1, 2020, 4:52am

on you mac select one at a time the dns servers you do not want to use and click the [-] button at the bottom of that window

Connection refused often means a rate limit of some kind. sometimes these can last from an hour to a day depending on the website

to fix the gateway you would want to pick reconfigure when running pihole -r not repair

jfb · January 1, 2020, 5:04am

Run pihole -r (select reconfigure) again and select the correct interface and gateway.

locnguyen · January 1, 2020, 5:27am

here's the new debug token: https://tricorder.pi-hole.net/99qhcen6rc

@technicalpyro unfortunately I cannot click on those. they are not selectable for some reason.
@jfb I just ran pihole -r reconfigure but it seems like it changes back to 192.168.0.189 to the ipv4 gateway
I've also ran pihole -g but i believe my list is still empty.


[i] Default IPv4 gateway: 192.168.0.189

192.168.0.10

* Pinging 192.168.0.189

192.168.0.10...

ping: 192.168.0.189

192.168.0.10: Name or service not known

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

[i] Default IPv6 gateway: fe80::d66e:eff:fe42:4048

fe80::d66e:eff:fe42:4048

* Pinging fe80::d66e:eff:fe42:4048

fe80::d66e:eff:fe42:4048...

ping: fe80::d66e:eff:fe42:4048

fe80::d66e:eff:fe42:4048: No address associated with hostname

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

*** [ DIAGNOSING ]: Ports in use

*:5900 vncserver- (IPv6)

*:5900 vncserver- (IPv4)

*:22 sshd (IPv4)

*:22 sshd (IPv6)

[*:80] is in use by lighttpd

[*:80] is in use by lighttpd

[*:53] is in use by pihole-FTL

[*:53] is in use by pihole-FTL

[127.0.0.1:4711] is in use by pihole-FTL

[[::1]:4711] is in use by pihole-FTL

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain

dig: '' is not a legal name (unexpected end of input)

[✗] Failed to resolve via localhost (127.0.0.1)

dig: '' is not a legal name (unexpected end of input)

[✗] Failed to resolve via Pi-hole (192.168.0.190)

[✗] Failed to resolve doubleclick.com via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain

dig: '' is not a legal name (unexpected end of input)

[✗] Failed to resolve via localhost (::1)

dig: '' is not a legal name (unexpected end of input)

[✗] Failed to resolve via Pi-hole (2600:8802:2100:378d:a4de:5d98:6b17:2a05)

[✓] doubleclick.com is 2607:f8b0:4007:802::200e via a remote, public DNS server (2001:4860:4860::8888)

*** [ DIAGNOSING ]: Pi-hole processes

[✓] lighttpd daemon is active

[✓] pihole-FTL daemon is active

Tesserax · January 1, 2020, 5:38am

If your Mac is configured as a DHCP client (it is by default) then the DNS addresses listed will be grayed out. That is because your router's DHCP server is providing the addresses. Your Mac is also getting IPv6 addresses, most likely because your ISP is providing you with IPv6 service.

locnguyen · January 1, 2020, 5:40am

@Tesserax I see, I was wondering what do you get when you run
$ nslookup flurry.com

Tesserax · January 1, 2020, 5:43am

@locnguyen Are you interested in the results for this command from my Mac or the Pi-hole?

locnguyen · January 1, 2020, 5:44am

@Tesserax from your pihole. I read that you're suppose to get refused.

I ran pihole -r to reconfigure the IPV4 Gateway but It just wont change it revert back to the wrong one every single time

Tesserax · January 1, 2020, 5:45am

@locnguyen Well it gets refused from both locations for me.

locnguyen · January 1, 2020, 5:46am

@Tesserax got it good to know. Thank you!

locnguyen · January 1, 2020, 5:52am

I've read that something in here might be pointing at the wrong ip but I dont think thats the case

pi@raspberrypi:~ $ sudo grep -v '#\|^$' /etc/dhcpcd.conf
hostname
clientid
persistent
option rapid_commit
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
option interface_mtu
require dhcp_server_identifier
slaac private
interface eth0
        static ip_address=192.168.0.190/24
        static routers=192.168.0.10
        static domain_name_servers=127.0.0.1

Tesserax · January 1, 2020, 5:52am

@locnguyen Well it appears that you may have some type of network issue that is preventing the Pi-hole from recognizing your network's gateway address. For that, I probably won't be able to help you as my network is based on Ubiquiti UniFi hardware.

You may need to go back to "square one" and re-install Raspbian on your RPi, then see if it can communicate with the Internet. Once verified, try installing Pi-hole again. Good luck! ... and, Happy New Year!

locnguyen · January 1, 2020, 5:54am

@Tesserax wow thats awesome. My goal/dream to have a Ubiquiti setup.
Thank you kind sir! Happy new year to you as well!

locnguyen · January 1, 2020, 9:34am

@Tesserax @jfb
I've redone everything, following this guide

now I am facing some different issues...
ads still show up on other devices than the pihole
here's the new token
https://tricorder.pi-hole.net/0yhu3jpabh

locnguyen · January 1, 2020, 8:42pm

I'm stuck.. Dont really know what to do.