Please follow the below template, it will help us to help you!
If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx, apache2 or another reverse proxy, or there is some other aspect of your install that is customised) - please use the Community Help category.
Expected Behaviour:
I expect no error messages to be displayed after running the following command: systemctl status unbound.service
Please include as much detail relevant to your system/install as possible including, but not limited to:
- Operating System (Family and Version) - Ubuntu
- Hardware - Virtual Machine running on Hyper-V through Windows Server 2022
- Docker compose file or Docker run command - N/A
- Docker engine version - N/A
Actual Behaviour:
When running the following command, systemctl status unbound.server, I receive the following error messages:
maniejv@maniejv-ubuntu-VM:~$ systemctl status unbound.service
Warning: The unit file, source configuration file or drop-ins of unbound.service changed on disk. Run 'systemctl daemon-reload' to reload units.
× unbound.service - Unbound DNS server
Loaded: loaded (/usr/lib/systemd/system/unbound.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Tue 2025-07-22 18:58:27 EDT; 22min ago
Docs: man:unbound(8)
Main PID: 2251 (code=exited, status=1/FAILURE)
CPU: 14ms
Jul 22 18:58:27 maniejv-ubuntu-VM systemd[1]: unbound.service: Scheduled restart job, restart counter is at 5.
Jul 22 18:58:27 maniejv-ubuntu-VM systemd[1]: unbound.service: Start request repeated too quickly.
Jul 22 18:58:27 maniejv-ubuntu-VM systemd[1]: unbound.service: Failed with result 'exit-code'.
Jul 22 18:58:27 maniejv-ubuntu-VM systemd[1]: Failed to start unbound.service - Unbound DNS server.
Debug Token:
Explicit debug log removed by developer and made private.