Unbound problems

[PA3DSS]

@jfb

service unbound restart

I installed pihole yesterday from cratch with bullseye on the raspberry pi, i get this failure:

root@206:/etc/unbound/unbound.conf.d# service unbound restart
Job for unbound.service failed because the control process exited with error code.
See "systemctl status unbound.service" and "journalctl -xe" for details.
root@206:/etc/unbound/unbound.conf.d#

What i gave to do to resolve this ?
my debug log
https://tricorder.pi-hole.net/TVA147JR/

[wd9895]

Sorry, I can not read your debug as I'm no Mod.
But did you try the optional part at the on of the documentation for Unbound?
https://docs.pi-hole.net/guides/dns/unbound/

[Moto]

did you mean sudo service unbound restart

When a moderator sees this he will probably ask you to post the output of the following commands from the Pi terminal:

unbound-checkconf

sudo grep -v '#\|^$' -R /etc/unbound/unbound.conf*

sudo service unbound status

It might speed things up if you don't wait for him to ask.

[Moto]

and once you have it running , have a read of:

DNS leak test shows Google IP addresses when using unbound

Expected Behaviour: DNS leak test should only show my own IP address Actual Behaviour: 6 servers were found when I ran the standard test on https://www.dnsleaktest.com. All of them were Google IP addresses even though I already unchecked Google in the Upstream DNS Servers setting and only put 127.0.0.1#5335 as Upstream DNS Server. I had also installed unbound according to the pihole documentation and it passed the DNSSEC validations. Debug Token: https://tricorder.pi-hole.net/dQiOT2zv/

[jfb]

@PA3DSS

See "systemctl status unbound.service" and "journalctl -xe" for details.

Additionally, did you do this?

[PA3DSS]

@PA3DSS

systemctl status unbound.service

pi@206:~ $ systemctl status unbound.service
● unbound.service - Unbound DNS server
Loaded: loaded (/lib/systemd/system/unbound.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2023-01-05 15:28:43 CET; 21h ago
Docs: man:unbound(8)
Process: 24289 ExecStartPre=/usr/lib/unbound/package-helper chroot_setup (code=exited, status=0/SUCCESS)
Process: 24292 ExecStartPre=/usr/lib/unbound/package-helper root_trust_anchor_update (code=exited, status=0/SUCCESS)
Process: 24295 ExecStart=/usr/sbin/unbound -d -p $DAEMON_OPTS (code=exited, status=1/FAILURE)
Process: 24296 ExecStopPost=/usr/lib/unbound/package-helper chroot_teardown (code=exited, status=0/SUCCESS)
Main PID: 24295 (code=exited, status=1/FAILURE)
CPU: 108ms

Jan 05 15:28:43 206 systemd[1]: unbound.service: Scheduled restart job, restart counter is at 5.
Jan 05 15:28:43 206 systemd[1]: Stopped Unbound DNS server.
Jan 05 15:28:43 206 systemd[1]: unbound.service: Start request repeated too quickly.
Jan 05 15:28:43 206 systemd[1]: unbound.service: Failed with result 'exit-code'.
Jan 05 15:28:43 206 systemd[1]: Failed to start Unbound DNS server.
pi@206:~ $

sudo journalctl -xe gives the next only last lines:

░░ The job identifier is 10385.
Jan 06 12:54:49 206 kernel: hwmon hwmon1: Undervoltage detected!
Jan 06 12:54:53 206 kernel: hwmon hwmon1: Voltage normalised
Jan 06 12:56:37 206 sudo[4336]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/journalctl -xe
Jan 06 12:56:37 206 sudo[4336]: pam_unix(sudo:session): session opened for user root(uid=0) by pi(uid=1000)