one issue I see with the 'bind' package itself once it's being installed, systemd did not reload the units on disk and simply does not know the service 'named' after issuing systemctl daemon-reload, the named service is known >> sudo zypper in bind >Loading repository data... >Reading installed packages... >Resolving package dependencies... > >The following NEW package is going to be installed: > bind > >1 new package to install. >Overall download size: 351.8 KiB. Already cached: 0 B. After the operation, additional 812.4 KiB will be used. >Continue? [y/n/...? shows all options] (y): >Retrieving package bind-9.10.4P5-26.2.x86_64 (1/1), 351.8 KiB (812.4 KiB unpacked) >Retrieving: bind-9.10.4P5-26.2.x86_64.rpm ..............................................................................................................................................[done] >Checking for file conflicts: ...........................................................................................................................................................[done] >(1/1) Installing: bind-9.10.4P5-26.2.x86_64 ............................................................................................................................................[done] >Additional rpm output: >Updating /etc/sysconfig/named ... > > >dimstar@zeus:~/Documents/git/websites/www.videolan.org/vlc> systemctl status named >Unit named.service could not be found. >dimstar@zeus:~/Documents/git/websites/www.videolan.org/vlc> sudo systemctl daemon-reload >dimstar@zeus:~/Documents/git/websites/www.videolan.org/vlc> systemctl status named >��� named.service - LSB: Domain Name System (DNS) server, named > Loaded: loaded (/etc/init.d/named; generated; vendor preset: disabled) > Active: inactive (dead) > Docs: man:systemd-sysv-generator(8) This should be a generic issue in packages bringing sysV init files - as we do not trigger systemctl daemon-reload there (but likely should!)