This is the contents of use-extended-statistics.conf:
# DEFINE SERVER
server:
# EXTENDED STATISTICS
# Note: Set desired verbosity
# use-entended-statistics.conf is called after unbound.conf
# so we can override the verbosity set there
# Verbosity levels are
# 1 - operational information
# 2 - detailed operational information
# 3 - query level information
# 4 - algorithm level information
# 5 - client level information
verbosity: 1
# Note: Number of seconds between statistics log updates
# Rarely required often, but needing to be fresh when it
# is, I have chosen ten minutes as my 'sweet spot'
statistics-interval: 600
# Note: Enable extended statistics
extended-statistics: yes
# Note: Enable cumulative statistics
statistics-cumulative: yes
Didn't see those files anywhere in the unbound package and dpkg-query: no path found matching pattern *use-extended-statistics.conf* was returned for looking in all packages.
Okay, okay, okay...those results are bringing back memories from when I originally installed Pihole and Unbound 3-4 years ago. I think I followed a guide that guy made and it resulted in those config files based on "their setup".
I think I should just probably uninstall Pihole and Unbound and start over.
Yeah, this current install of Pihole and unbound was from 3 years ago and I had that Reddit post bookmarked in a "Pihole" folder. He mentions his Github in that Reddit post and I guess I saw something that convinced me to also add his configs, too. I don't really remember all the details from the install from that long ago.
But! At least you found where they came from. It was from his repo and I do recall his username now.
Hmm...already an issue from the first step. I purged all previous unbound installs and deleted all config files and directories.
root@DietPi:/etc# sudo apt install unbound
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
unbound-anchor
The following NEW packages will be installed:
unbound unbound-anchor
0 upgraded, 2 newly installed, 0 to remove and 1 not upgraded.
Need to get 820 kB of archives.
After this operation, 3,851 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://mirror.umd.edu/raspbian/raspbian buster/main armhf unbound-anchor armhf 1.9.0-2+deb10u3 [146 kB]
Get:2 http://mirror.umd.edu/raspbian/raspbian buster/main armhf unbound armhf 1.9.0-2+deb10u3 [674 kB]
Fetched 820 kB in 1s (1,004 kB/s)
Selecting previously unselected package unbound-anchor.
(Reading database ... 76173 files and directories currently installed.)
Preparing to unpack .../unbound-anchor_1.9.0-2+deb10u3_armhf.deb ...
Unpacking unbound-anchor (1.9.0-2+deb10u3) ...
Selecting previously unselected package unbound.
Preparing to unpack .../unbound_1.9.0-2+deb10u3_armhf.deb ...
Unpacking unbound (1.9.0-2+deb10u3) ...
Setting up unbound-anchor (1.9.0-2+deb10u3) ...
Setting up unbound (1.9.0-2+deb10u3) ...
Created symlink /etc/systemd/system/multi-user.target.wants/unbound.service → /lib/systemd/system/unbound.service.
Created symlink /etc/systemd/system/unbound.service.wants/unbound-resolvconf.service → /lib/systemd/system/unbound-resolvconf.service.
Job for unbound.service failed because the control process exited with error code.
See "systemctl status unbound.service" and "journalctl -xe" for details.
Job for unbound.service failed because the control process exited with error code.
See "systemctl status unbound.service" and "journalctl -xe" for details.
invoke-rc.d: initscript unbound, action "start" failed.
● unbound.service - Unbound DNS server
Loaded: loaded (/lib/systemd/system/unbound.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2023-08-03 19:00:20 EDT; 33ms ago
Docs: man:unbound(8)
Process: 3054 ExecStartPre=/usr/lib/unbound/package-helper chroot_setup (code=exited, status=0/SUCCESS)
Process: 3057 ExecStartPre=/usr/lib/unbound/package-helper root_trust_anchor_update (code=exited, status=0/SUCCESS)
Process: 3061 ExecStart=/usr/sbin/unbound -d $DAEMON_OPTS (code=exited, status=1/FAILURE)
Main PID: 3061 (code=exited, status=1/FAILURE)
Processing triggers for systemd (241-7~deb10u9+rpi1) ...
This screenshot is from a private browser window (Firefox - I used a private browser session because I didn't want the ads to be blocked by NoScript or uBlock Origin extensions) and the entire page is encircled with ads. Why isn't the Pihole blocking this? This screenshot was from my laptop that has the Pihole set as its DNS.
This is the same thing I was seeing on my iPhone earlier in the day where it just didn't seem like the Pihole was blocking anything, even though these entries are showing in the query log:
The first domain from the first screenshot should have been blocked:
pi@ph5b:~ $ pihole -q adsfs.oppomobile.com
Match found in https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts:
adsfs.oppomobile.com
pi@ph5b:~ $ host adsfs.oppomobile.com localhost
Using domain server:
Name: localhost
Address: ::1#53
Aliases:
adsfs.oppomobile.com has address 0.0.0.0
adsfs.oppomobile.com has IPv6 address ::
pi@ph5b:~ $ pihole -t
[..]
Aug 4 02:53:07: query[A] adsfs.oppomobile.com from ::1
Aug 4 02:53:07: gravity blocked adsfs.oppomobile.com is 0.0.0.0
Aug 4 02:53:08: query[AAAA] adsfs.oppomobile.com from ::1
Aug 4 02:53:08: gravity blocked adsfs.oppomobile.com is ::
Aug 4 02:53:08: query[MX] adsfs.oppomobile.com from ::1
Aug 4 02:53:08: gravity blocked adsfs.oppomobile.com is NODATA
Upload a fresh debug log and post only the resulting token URL so the mods/devs can have a look if something wrong ... maybe you configured "groups"?