Hallo,
kann mir vielleicht jemand beim Einrichten von Unbound in der VM helfen?
VM mit Debian läuft, Unbound ist installiert, bekomme es aber nicht gestartet, bei unbound-checkconf kommt:
root@unbound:/etc/unbound# unbound-checkconf
/etc/unbound/“/etc/unbound/root.hints”: No such file or directory
[1615392571] unbound-checkconf[1001:0] fatal error: file with root-hints: ““/etc/unbound/root.hints”” does not exist
root@unbound:/etc/unbound#
root@unbound:/etc/unbound# service unbound start
Job for unbound.service failed because the control process exited with error code.
See “systemctl status unbound.service” and “journalctl -xe” for details.
root@unbound:/etc/unbound# journalctl -xe
Mär 10 17:12:05 unbound systemd[1]: unbound.service: Service RestartSec=100ms expired, scheduling restart.
Mär 10 17:12:05 unbound systemd[1]: unbound.service: Scheduled restart job, restart counter is at 5.
— Subject: Automatic restarting of a unit has been scheduled
— Defined-By: systemd
— Support: https://www.debian.org/support
—
— Automatic restarting of the unit unbound.service has been scheduled, as the result for
— the configured Restart= setting for the unit.
Mär 10 17:12:05 unbound systemd[1]: Stopped Unbound DNS server.
— Subject: A stop job for unit unbound.service has finished
— Defined-By: systemd
— Support: https://www.debian.org/support
—
— A stop job for unit unbound.service has finished.
—
— The job identifier is 1692 and the job result is done.
Mär 10 17:12:05 unbound systemd[1]: unbound.service: Start request repeated too quickly.
Mär 10 17:12:05 unbound systemd[1]: unbound.service: Failed with result ‘exit-code’.
— Subject: Unit failed
— Defined-By: systemd
— Support: https://www.debian.org/support
—
— The unit unbound.service has entered the ‘failed’ state with result ‘exit-code’.
Mär 10 17:12:05 unbound systemd[1]: Failed to start Unbound DNS server.
— Subject: A start job for unit unbound.service has failed
— Defined-By: systemd
— Support: https://www.debian.org/support
—
— A start job for unit unbound.service has finished with a failure.
—
— The job identifier is 1692 and the job result is failed.
Mär 10 17:12:05 unbound systemd[1]: Condition check resulted in Unbound DNS server via resolvconf being skipped.
— Subject: A start job for unit unbound-resolvconf.service has finished successfully
— Defined-By: systemd
— Support: https://www.debian.org/support
—
— A start job for unit unbound-resolvconf.service has finished successfully.
—
— The job identifier is 1753.
Die Dateien und Verzeichnisse sind alle da:
root@unbound:/etc/unbound# ls -all
insgesamt 36
drwxr-xr-x 3 root root 4096 Mär 10 17:00 .
drwxr-xr-x 74 root root 4096 Mär 10 16:37 ..
-rw-r–r– 1 root root 3316 Feb 17 17:26 root.hints
-rw-r–r– 1 root root 505 Mär 10 17:00 unbound.conf
drwxr-xr-x 2 root root 4096 Mär 10 16:51 unbound.conf.d
-rw-r—– 1 root root 2459 Mär 10 16:36 unbound_control.key
-rw-r—– 1 root root 1342 Mär 10 16:36 unbound_control.pem
-rw-r—– 1 root root 2455 Mär 10 16:36 unbound_server.key
-rw-r—– 1 root root 1334 Mär 10 16:36 unbound_server.pem
kann mir vielleicht jemand beim Einrichten von Unbound in der VM helfen?
VM mit Debian läuft, Unbound ist installiert, bekomme es aber nicht gestartet, bei unbound-checkconf kommt:
root@unbound:/etc/unbound# unbound-checkconf
/etc/unbound/“/etc/unbound/root.hints”: No such file or directory
[1615392571] unbound-checkconf[1001:0] fatal error: file with root-hints: ““/etc/unbound/root.hints”” does not exist
root@unbound:/etc/unbound#
root@unbound:/etc/unbound# service unbound start
Job for unbound.service failed because the control process exited with error code.
See “systemctl status unbound.service” and “journalctl -xe” for details.
root@unbound:/etc/unbound# journalctl -xe
Mär 10 17:12:05 unbound systemd[1]: unbound.service: Service RestartSec=100ms expired, scheduling restart.
Mär 10 17:12:05 unbound systemd[1]: unbound.service: Scheduled restart job, restart counter is at 5.
— Subject: Automatic restarting of a unit has been scheduled
— Defined-By: systemd
— Support: https://www.debian.org/support
—
— Automatic restarting of the unit unbound.service has been scheduled, as the result for
— the configured Restart= setting for the unit.
Mär 10 17:12:05 unbound systemd[1]: Stopped Unbound DNS server.
— Subject: A stop job for unit unbound.service has finished
— Defined-By: systemd
— Support: https://www.debian.org/support
—
— A stop job for unit unbound.service has finished.
—
— The job identifier is 1692 and the job result is done.
Mär 10 17:12:05 unbound systemd[1]: unbound.service: Start request repeated too quickly.
Mär 10 17:12:05 unbound systemd[1]: unbound.service: Failed with result ‘exit-code’.
— Subject: Unit failed
— Defined-By: systemd
— Support: https://www.debian.org/support
—
— The unit unbound.service has entered the ‘failed’ state with result ‘exit-code’.
Mär 10 17:12:05 unbound systemd[1]: Failed to start Unbound DNS server.
— Subject: A start job for unit unbound.service has failed
— Defined-By: systemd
— Support: https://www.debian.org/support
—
— A start job for unit unbound.service has finished with a failure.
—
— The job identifier is 1692 and the job result is failed.
Mär 10 17:12:05 unbound systemd[1]: Condition check resulted in Unbound DNS server via resolvconf being skipped.
— Subject: A start job for unit unbound-resolvconf.service has finished successfully
— Defined-By: systemd
— Support: https://www.debian.org/support
—
— A start job for unit unbound-resolvconf.service has finished successfully.
—
— The job identifier is 1753.
Die Dateien und Verzeichnisse sind alle da:
root@unbound:/etc/unbound# ls -all
insgesamt 36
drwxr-xr-x 3 root root 4096 Mär 10 17:00 .
drwxr-xr-x 74 root root 4096 Mär 10 16:37 ..
-rw-r–r– 1 root root 3316 Feb 17 17:26 root.hints
-rw-r–r– 1 root root 505 Mär 10 17:00 unbound.conf
drwxr-xr-x 2 root root 4096 Mär 10 16:51 unbound.conf.d
-rw-r—– 1 root root 2459 Mär 10 16:36 unbound_control.key
-rw-r—– 1 root root 1342 Mär 10 16:36 unbound_control.pem
-rw-r—– 1 root root 2455 Mär 10 16:36 unbound_server.key
-rw-r—– 1 root root 1334 Mär 10 16:36 unbound_server.pem
