Before I had unbound working on Core v6.0.3, FTL v6.0.2, Web interface v6.0.1
However, after upgrading the Core version to 6.0.4, unbound doesn't work using 127.0.0.1#5335. If I change to using a different upstream server like Cloudflare, internet works. Any ideas or fixes will be much appreciated, thank you guys for the hard work 
I experienced no issues.
No issues here.
Can you check if unbound is working when you query it directly.
Could it be because of this? For your custom DNS server settings, do you just have '127.0.0.1#5335' ?
Oou ok, I think I found out some issues. I realised unbound service wasn’t running. Here's the output: systemctl status unbound
● unbound.service - Unbound DNS server
Loaded: loaded (/lib/systemd/system/unbound.service; disabled; vendor preset: enabled)
Active: inactive (dead)
Docs: man:unbound(8)
After enabling it using: sudo systemctl enable unbound
Synchronizing state of unbound.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable unbound
Created symlink /etc/systemd/system/multi-user.target.wants/unbound.service → /lib/systemd/system/unbound.service.
I rebooted and now I see on the pihole dashboard "DNS Server Failure" , doesn't seem to show the domains on list
Check from commandline:
dig @127.0.0.1 -p 5335 google.com
Righto, here's the output
; <<>> DiG 9.16.50-Debian <<>> @127.0.0.1 -p 5335 google.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached
I ran this command and got this output: systemctl status unbound
● unbound.service - Unbound DNS server
Loaded: loaded (/lib/systemd/system/unbound.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2025-02-25 21:43:52 AEDT; 4min 6s ago
Docs: man:unbound(8)
Process: 548 ExecStartPre=/usr/lib/unbound/package-helper chroot_setup (code=exited, status=1/FAILURE)
Process: 624 ExecStartPre=/usr/lib/unbound/package-helper root_trust_anchor_update (code=exited, status=1/FAILURE)
Main PID: 646 (unbound)
Tasks: 1 (limit: 3933)
CPU: 255ms
CGroup: /system.slice/unbound.service
└─646 /usr/sbin/unbound -d -p
Feb 25 21:43:51 raspberrypi systemd[1]: Starting Unbound DNS server...
Feb 25 21:43:51 raspberrypi package-helper[555]: [1740480231] unbound-checkconf[555:0] error: Could not open /etc/unbound/unbound.conf: No such file or directory
Feb 25 21:43:52 raspberrypi package-helper[635]: [1740480232] unbound-checkconf[635:0] error: Could not open /etc/unbound/unbound.conf: No such file or directory
Feb 25 21:43:52 raspberrypi unbound[646]: [1740480232] unbound[646:0] error: Could not open /etc/unbound/unbound.conf: No such file or directory
Feb 25 21:43:52 raspberrypi unbound[646]: [1740480232] unbound[646:0] warning: Continuing with default config settings
Feb 25 21:43:52 raspberrypi unbound[646]: [646:0] notice: init module 0: subnet
Feb 25 21:43:52 raspberrypi unbound[646]: [646:0] notice: init module 1: validator
Feb 25 21:43:52 raspberrypi unbound[646]: [646:0] notice: init module 2: iterator
Feb 25 21:43:52 raspberrypi unbound[646]: [646:0] info: start of service (unbound 1.13.1).
Feb 25 21:43:52 raspberrypi systemd[1]: Started Unbound DNS server.
Alrighty, I finally fixed the issue. Got unbound working now. Thanks everyone who contributed. Solution to this can be found here: [SOLVED] Unbound failing on install
Just to be sure compare your configuration to unbound - Pi-hole documentation and make sure everything is at it should be to avoid future issues 
1 Like
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.