09.11.2020 18:59, cagsm пишет:
Hi list,
already came across this oddity multiple times in recent weeks:
named/bind bug? multiple systems, 15.2, after reboot, named service wouldnt autostart
people at sites calling me that something doesnt work with their internet. turns out the named/bind resolver on the linux machine was not started up.
the status initially within few minutes after a reboot would show e.g.
sudo systemctl status named.service [sudo] password for root: ● named.service - Berkeley Internet Name Domain (DNS) Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled) Active: inactive (dead)
Nov 09 00:24:41 tux systemd[1]: named.service: Job named.service/start deleted to break ordering cycle starting with nss-lookup.target/start
I could then manually start up the named by
sudo systemctl start named.service
then showing it status as
sudo systemctl status named.service ● named.service - Berkeley Internet Name Domain (DNS) Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled) Active: active (running) since Mon 2020-11-09 00:52:49 XYZT; 1s ago Process: 5010 ExecStart=/usr/sbin/named.init start (code=exited, status=0/SUCCESS) Main PID: 5048 (named) Tasks: 20 CGroup: /system.slice/named.service └─5048 /usr/sbin/named -t /var/lib/named -u named
.....
What happen?
https://forums.opensuse.org/showthread.php/545542-Systemd-nss_lookup-target-... IMHO time after DNS is redundant dependency. But someone needs to open bug report. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org