New pihole not blocking ads

Help
41

The router that I'm using is Sagemcom FWR226e.

I can go into a menu for DNS IPv4 to set the DNS, and when I set it to pihole it kicks off the internet until I set it to obtain DNS automatically. I can also go into Information and Settings menu of the router and set a manual DNS but that doesn't affect anything.

If I set, for example my phone, to pihole I don't get any internet access.

I do get get an error now for my pihole that says:

*Long-term load (15min avg) larger than number of processors: *1.1 > 1
This may slow down DNS resolution and can cause bottlenecks.

Here are my results for cat /etc/resolv.conf:

Generated by NetworkManager

search local.ftr
nameserver 9.9.9.9

For the ip -a I get a bunch of options that I'm not understanding.

42

sorry, its not ip -a but ip a I mistyped that.

43

Here are my results:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether b8:27:eb:ea:ba:d6 brd ff:ff:ff:ff:ff:ff
inet 192.168.254.24/24 brd 192.168.254.255 scope global dynamic noprefixroute wlan0
valid_lft 1514sec preferred_lft 1514sec
inet6 fda0:25f3:c62d:12c1:9362:ae17:8ed4:6f20/64 scope global dynamic noprefixroute
valid_lft 1604sec preferred_lft 1604sec
inet6 fe80::9474:ef30:8665:a58/64 scope link noprefixroute
valid_lft forever preferred_lft forever

44

Lets set aside the router for a moment and test the pihole. Your ip a command shows your ip as 192.168,254.24 . Was that set as static? If not it needs to be.

From the pihole run dig @localhost flurry.com This should return 0.0.0.0 in the answer section.

Also run dig @locahost pi-hole.net If this is working properly it should show 3.18.136.52 in the answer section.

45

The IP address for pihole (192.168.254.24) is statically assigned on my router.

For your first command this is what I received:

; <<>> DiG 9.18.24-1-Raspbian <<>> @localhost flurry.com
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28454
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;flurry.com. IN A

;; ANSWER SECTION:
flurry.com. 2 IN A 0.0.0.0

;; Query time: 10 msec
;; SERVER: ::1#53(localhost) (UDP)
;; WHEN: Fri May 10 18:19:11 CDT 2024
;; MSG SIZE rcvd: 55

For your second command I got this:

;; communications error to ::1#53: timed out
;; communications error to ::1#53: timed out
;; communications error to ::1#53: timed out
;; communications error to 127.0.0.1#53: timed out

; <<>> DiG 9.18.24-1-Raspbian <<>> @localhost pi-hole.net
; (2 servers found)
;; global options: +cmd
;; no servers could be reached

46

So that 1st test worked but send failed. From the pihole please run pihole status

47

Here are my results:

[✓] FTL is listening on port 53

  • [✓] UDP (IPv4)*

  • [✓] TCP (IPv4)*

  • [✓] UDP (IPv6)*

  • [✓] TCP (IPv6)*

  • [✓] Pi-hole blocking is enabled*

48

When you did the fresh install did you use the bookworm raspbian image? Just curious as it changes some of the networking commands.

From the pihole lets try pihole disable followed by dig@localhost pi-hole.net followed by pihole enable You just testing the results of resolving pi-hole.net with pihole off.

49

The fresh install is using the newest Bookworm raspian image.

Here are my results from what you wanted me to run:

;; communications error to 9.9.9.9#53: timed out
;; communications error to 9.9.9.9#53: timed out
;; communications error to 9.9.9.9#53: timed out

; <<>> DiG 9.18.24-1-Raspbian <<>> localhost pi-hole.net
;; global options: +cmd
;; no servers could be reached

;; communications error to 9.9.9.9#53: timed out
;; communications error to 9.9.9.9#53: timed out
;; communications error to 9.9.9.9#53: timed out
;; no servers could be reached

50

So if i'm understanding this correctly you ran pihole disable and it cameback with a timeout error? That makes no sense.

As this is a fresh install I would suggest reinstalling the OS using the same bookworm image but do not install pihole at all. Make sure your router is providing DNS to a resolver like 9.9.9.9 or 1.1.1.1 and we will make sure that networking on the pi is working as intended before installing pihole.

After you install the OS make sure you can run a sudo apt update and if thats ok, follow it with the sudo apt upgrade

If those work ok you can try a dig pi-hole.net and also a dig flurry.com and post those results.

If those work ok we can look to try the pihole install. If not, we can focus on the what might be going on with the OS / Raspberry pi itself.

51

I will work on that and get back with you.

I changed my DNS settings on my router to 1.1.1.1 AND 9.9.9.9 and my router is working happily off those for the time being.

52

When I try to dig pi-hole.net and flurry.com it returns with command not found.

53

You can install it using sudo apt install dnsutils

54

After doing that I ran the commands you wanted me to run before.

dig pi-hole.net:

; <<>> DiG 9.18.24-1-Raspbian <<>> pi-hole.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35727
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;pi-hole.net. IN A

;; ANSWER SECTION:
pi-hole.net. 300 IN A 3.18.136.52

;; Query time: 19 msec
;; SERVER: 192.168.254.254#53(192.168.254.254) (UDP)
;; WHEN: Sat May 11 16:19:13 CDT 2024
;; MSG SIZE rcvd: 56

dig flurry.com:

; <<>> DiG 9.18.24-1-Raspbian <<>> flurry.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38404
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;flurry.com. IN A

;; ANSWER SECTION:
flurry.com. 300 IN A 76.223.84.192
flurry.com. 300 IN A 13.248.158.7

;; Query time: 39 msec
;; SERVER: 192.168.254.254#53(192.168.254.254) (UDP)
;; WHEN: Sat May 11 16:19:24 CDT 2024
;; MSG SIZE rcvd: 71

55

What is the host 192.168.254.254? With nothing installed I would expect this to be your routers IP address.

56

That's correct, that is my router.

57

Gotcha. Usually its the 1st IP address so I wasn't sure.Those two domains resolved correctly. Lets install pihole using:

curl -sSL https://install.pi-hole.net | bash

But don't change the router to point to the the pihole just yet. We can test it first providing the install goes correctly.

58

Installation was successful and is now complete.

59

Awesome. Lets do some quick tests.

From the pi run dig @localhost pi-hole.net This should resolve to an ip.

Next run dig @localhost flurry.com this should return 0.0.0.0 indicating pihole blocked it.

If that works ok do the same thing from the pihole using the pihole ip address. So instead of dig @localhost flurry.com it would be dig flurry.com @piholes ip address.

If that works ok then do that same thing from a client. If the client doesn't have dig installed you can use nslookup flurry.com *piholes ip address*

You should also make sure you can access the webgui using piholes ip address/admin from a clients broswer.

60

Here are my results in order of your commands:

dig @localhost pi-hole.net

; <<>> DiG 9.18.24-1-Raspbian <<>> @localhost pi-hole.net
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1605
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;pi-hole.net. IN A

;; ANSWER SECTION:
pi-hole.net. 287 IN A 3.18.136.52

;; Query time: 39 msec
;; SERVER: ::1#53(localhost) (UDP)
;; WHEN: Sat May 11 17:21:01 CDT 2024
;; MSG SIZE rcvd: 56

dig flurry.com @192.168.254.24

; <<>> DiG 9.18.24-1-Raspbian <<>> flurry.com @192.168.254.24
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18867
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;flurry.com. IN A

;; ANSWER SECTION:
flurry.com. 2 IN A 0.0.0.0

;; Query time: 29 msec
;; SERVER: 192.168.254.24#53(192.168.254.24) (UDP)
;; WHEN: Sat May 11 17:22:40 CDT 2024
;; MSG SIZE rcvd: 55

nslookup flurry.com 192.168.254.24
Server: 192.168.254.24
Address: 192.168.254.24#53

Name: flurry.com
Address: 0.0.0.0
*Name: flurry.*com
Address: ::

I am also able to log in into the web console and I can see where it blocked flurry.com 5 times.