Updating to latest tumbleweed:

(185/220) Installation von: bind-9.10.3P2-14.1 ................[fertig]
Zus�tzliche RPM-Ausgabe:
Updating /etc/sysconfig/named ...
The unit files have no [Install] section. They are not meant to be enabled
using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
   .wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
   a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
   D-Bus, udev, scripted systemctl call, ...).


This is probably caused by
    systemctl preset named.service
in bind's %post.

The interesting part is:

systemctl cat named.service 
# /run/systemd/generator.late/named.service
# Automatically generated by systemd-sysv-generator

[Unit]
Documentation=man:systemd-sysv-generator(8)
SourcePath=/etc/init.d/named
Description=LSB: Domain Name System (DNS) server, named
Before=nss-lookup.target
After=network-online.target remote-fs.target ldap.service
Wants=nss-lookup.target network-online.target

[Service]
Type=forking
Restart=no
TimeoutSec=5min
IgnoreSIGPIPE=no
KillMode=process
GuessMainPID=no
RemainAfterExit=yes
ExecStart=/etc/init.d/named start
ExecStop=/etc/init.d/named stop
ExecReload=/etc/init.d/named reload


so this file is autogenerated - and that's also the reason why I think this is
a systemd bug ;-)