After a few hours I finally installed pi-hole on debian 12 with an apache server. Unfortunately, I cannot configure unbound to work. After entering pi-hole/dns/Custom 1 (IPv4) 127.0.0.1#5335 in the menu, dns does not respond. Ping by IP works, but after entering the domain name it no longer works. In the query log I have a servfail entry.
P.S. I use NetworkMenager for network configuration and do not have a /etc/resolve.conf file
Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:
pihole -d
or do it through the Web interface:
Tools > Generate Debug Log
Your debug log shows that Pi-hole is working properly. Now, let's take a look at unbound.
Is either unbound or Pi-hole running in a Docker container? Or, are they both running on bare metal?
Please post the output of the following command from the Pi terminal:
unbound-checkconf
sudo grep -v '#\|^$' -R /etc/unbound/unbound.conf*
They are installed directly in the Debian system.
sudo grep -v '#\|^$' -R /etc/unbound/unbound.conf*
/etc/unbound/unbound.conf:include-toplevel: "/etc/unbound/unbound.conf.d/*.conf"
/etc/unbound/unbound.conf.d/root-auto-trust-anchor-file.conf:server:
/etc/unbound/unbound.conf.d/root-auto-trust-anchor-file.conf: auto-trust-anchor-file: "/var/lib/unbound/root.key"
/etc/unbound/unbound.conf.d/pi-hole.conf:server:
/etc/unbound/unbound.conf.d/pi-hole.conf: verbosity: 0
/etc/unbound/unbound.conf.d/pi-hole.conf: interface: 127.0.0.1
/etc/unbound/unbound.conf.d/pi-hole.conf: port: 5335
/etc/unbound/unbound.conf.d/pi-hole.conf: do-ip4: yes
/etc/unbound/unbound.conf.d/pi-hole.conf: do-udp: yes
/etc/unbound/unbound.conf.d/pi-hole.conf: do-tcp: yes
/etc/unbound/unbound.conf.d/pi-hole.conf: do-ip6: no
/etc/unbound/unbound.conf.d/pi-hole.conf: prefer-ip6: no
/etc/unbound/unbound.conf.d/pi-hole.conf: harden-glue: yes
/etc/unbound/unbound.conf.d/pi-hole.conf: harden-dnssec-stripped: yes
/etc/unbound/unbound.conf.d/pi-hole.conf: use-caps-for-id: no
/etc/unbound/unbound.conf.d/pi-hole.conf: edns-buffer-size: 1232
/etc/unbound/unbound.conf.d/pi-hole.conf: prefetch: yes
/etc/unbound/unbound.conf.d/pi-hole.conf: num-threads: 1
/etc/unbound/unbound.conf.d/pi-hole.conf: so-rcvbuf: 1m
/etc/unbound/unbound.conf.d/pi-hole.conf: private-address: 192.168.0.0/16
/etc/unbound/unbound.conf.d/pi-hole.conf: private-address: 169.254.0.0/16
/etc/unbound/unbound.conf.d/pi-hole.conf: private-address: 172.16.0.0/12
/etc/unbound/unbound.conf.d/pi-hole.conf: private-address: 10.0.0.0/8
/etc/unbound/unbound.conf.d/pi-hole.conf: private-address: fd00::/8
/etc/unbound/unbound.conf.d/pi-hole.conf: private-address: fe80::/10
/etc/unbound/unbound.conf.d/pi-hole.conf: serve-expired: no
/etc/unbound/unbound.conf.d/pi-hole.conf: prefetch: no
/etc/unbound/unbound.conf.d/remote-control.conf:remote-control:
/etc/unbound/unbound.conf.d/remote-control.conf: control-enable: yes
/etc/unbound/unbound.conf.d/remote-control.conf: control-interface: /run/unbound.ctl
unbound-checkconf: no errors in /etc/unbound/unbound.conf
With a clean install of Debian 12 you need to make sure systemd-resolved is installed to create a /etc/resolv.conf file. This isn't an issue If upgrading from Debian 11.
When systemd-resolved was running, pi-hole reported an error about port 535 being used by dnsmasq. Pihole-ftl did not start. After stopping systemd-resolved:
sudo systemctl stop systemd-resolved
sudo systemctl disable systemd-resolved
Pi-Hole started working without any problems
Unfortunately, I see that pi-hole + debian and apache create a lot of problems.
I gave up and uninstalled pi-hole. 
I didn't have such problems with another blocker.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.