works for me - but why network-online.target is replaced with network.target - that is nonsense - network.target is not enabled here looking at systemctl list-units while network-online.target IS
@hreindl This is inetntional, since BIND does not need to wait for the network to be fully set up. network.tagrget is passive unit and therefore it is not listed in the output of systemctl list-units. It is expected, that the network configuration management software will pull the target into the transaction. More info in https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
"BIND does not need to wait for the network to be fully set up" is a naive approach for simple setups but not true on others which may break now - luckily i have my own systemd-units below /etc/systemd/systemd/ for anything i care about (and if it's only to use "CapabilityBoundingSet" and "ReadOnlyDirectories" which is available for years now and Fedora still does a terrible bad job to use it for services
@hreindl BIND listens on RTNETLINK for information about new addresses and binds to them in case they are allowed by the configuration. Therefore there is no need to wait for network-online.target. If you have some specific issues, please file a Bug.
the RTNETLINK stuff typically don't work in realtime and so if on a server for your network named is supposed to forward anything but the internal zone to the dns server on the other side of the openvpn-tunnel and follow-up services needs name resolving they fail - however, as said i don't care much about fedora systemd-units below /usr
This update has been submitted for stable by bodhi.
This update has been submitted for testing by thozza.
works for me - but why network-online.target is replaced with network.target - that is nonsense - network.target is not enabled here looking at systemctl list-units while network-online.target IS
@hreindl This is inetntional, since BIND does not need to wait for the network to be fully set up. network.tagrget is passive unit and therefore it is not listed in the output of systemctl list-units. It is expected, that the network configuration management software will pull the target into the transaction. More info in https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
"BIND does not need to wait for the network to be fully set up" is a naive approach for simple setups but not true on others which may break now - luckily i have my own systemd-units below /etc/systemd/systemd/ for anything i care about (and if it's only to use "CapabilityBoundingSet" and "ReadOnlyDirectories" which is available for years now and Fedora still does a terrible bad job to use it for services
This update has been pushed to testing.
Seems to work here on x86_64.
@hreindl BIND listens on RTNETLINK for information about new addresses and binds to them in case they are allowed by the configuration. Therefore there is no need to wait for network-online.target. If you have some specific issues, please file a Bug.
the RTNETLINK stuff typically don't work in realtime and so if on a server for your network named is supposed to forward anything but the internal zone to the dns server on the other side of the openvpn-tunnel and follow-up services needs name resolving they fail - however, as said i don't care much about fedora systemd-units below /usr
This update has been submitted for stable by bodhi.
works for me
This update has been pushed to stable.