Description of problem: named 9.9.1-P1 or P2 does not listen on eth0 as something happen and start before of network correct init Version-Release number of selected component (if applicable): 9.9.1-P1 or 9.9.1-P2 Fedora 17 done yum update on 26 july 2012 and got in the problem!. System installed 4 july 2012 and was fine How reproducible: 9.9.1-P1 or 9.9.1-P2 Fedora 17 done yum update on 26 july 2012 and got in the problem!. System installed 4 july 2012 and was fine I find many issues on the net about it as one for all http://www.linuxquestions.org/questions/linux-server-73/named-does-not-listen-on-eth0-right-after-boot-659899/ Steps to Reproduce: 1. install fc17 2. sure to make yum update 3. if after system load I log inside and do via systemctl or service statement a stop and start of ISC NAMED, it is all ok and inside /var/log/messages write to listen not only on lo, 127.0.0.1 but on eth0 if interface too Actual results: Expected results: Additional info:
possible fix as stated on https://bugzilla.redhat.com/show_bug.cgi?id=837173 Fix: Change the four occurrences of "/sbin/systemctl" in /etc/NetworkManager/dispatcher.d/13-named to "/usr/bin/systemctl". I even changed line 1 as I don't use chroot by now in all case a 'locate systemctl' say that systemctl is not inside /sbin but inside /usr/bin so all statements inside /etc/NetworkManager/dispatcher.d/13-named *FAIL* please let me to know
That file comes from bind.
*** This bug has been marked as a duplicate of bug 837173 ***