Description of problem: named starts before network initialization is complete
Version-Release number of selected component (if applicable):
How reproducible: Configure named to listen on explicit static interface address.
Steps to Reproduce:
1. reboot system
Actual results: named generates an error indicating its interface does not exist.
Expected results: named starts
Additional info: This is a generic problem with all services binding to explicit interface addresses and depending on network.target only. network.target does not make sure that all statically configured interfaces are up. Onle network-online.target does that. Therefore the solution for all configurable services not supporting IP_FREEBIND is to change the dependency
from network.target to a depedency on network-online.target:
Other network services are affected as well so this bug report is only one in a row.
*** This bug has been marked as a duplicate of bug 1117086 ***