Hi If network is not available or started because a wrong start-order (https://bugzilla.redhat.com/show_bug.cgi?id=381951) bind resloves only its own zones and must be restarted after network is available. I do not really understand WHY a alpha-version is included in stable fedora 8! bind-9.5.0-16.a6.fc8
(In reply to comment #0) > Hi > > If network is not available or started because a wrong start-order > (https://bugzilla.redhat.com/show_bug.cgi?id=381951) bind resloves only its own > zones and must be restarted after network is available. What you mean with "bind resloves only its own zones"? Could you please attach log? I don't think this is bind problem because it needs network started (Require-Start statement from initscript) > > I do not really understand WHY a alpha-version is included in stable fedora 8! > bind-9.5.0-16.a6.fc8 Answer is GSS-TSIG.
This is a problem of bind and new inf F8 in this way There plays some problems of F8 together and it will hit only notebooks with WLAN in this way. However - If the exists no network connection that was never a problem fpr bind, now it must be restarted instead of resolving from the moment network-connection exists.... * wpa_supplicant needs messagebus * wpa_supplicant will sterted at 11, loh nefore messagebus * Some idiotic software places bind ervy change in system-config-services directly after messagebus * Damned how should anyone solve this by renaming the Init-Symlinks and put network between messagebus and bind what is the only solution I hope there will be a solution, FC6 and Fedora 7 had none of this problemls and again: why you provide a alpha-version of bind with fedora?
(In reply to comment #2) > This is a problem of bind and new inf F8 in this way > There plays some problems of F8 together and it will hit only notebooks with > WLAN in this way. > > However - If the exists no network connection that was never a problem fpr bind, > now it must be restarted instead of resolving from the moment network-connection > exists.... > > * wpa_supplicant needs messagebus > * wpa_supplicant will sterted at 11, loh nefore messagebus > * Some idiotic software places bind ervy change in system-config-services > directly after messagebus > * Damned how should anyone solve this by renaming the Init-Symlinks and put > network between messagebus and bind what is the only solution > > I hope there will be a solution, FC6 and Fedora 7 had none of this problemls I'm not able to do anything with this. This has to be fixed in wpa_supplicant as written in https://bugzilla.redhat.com/show_bug.cgi?id=381951#c6 and > again: why you provide a alpha-version of bind with fedora? > Please see GSS-TSIG feature. It is avaliable only in BIND 9.5 . With this feature BIND could be integrated into Active Directory as master DNS server. Next interesting feature is stats export through http server integrated into bind. These two features are reason why I've put BIND 9.5 into F8 instead 9.4 . And when software is alpha version it doesn't mean it is unstable. It means it is under development. *** This bug has been marked as a duplicate of 381951 ***