Red Hat Bugzilla – Bug 381571
NetworkManager starts bind needlessly
Last modified: 2008-01-06 20:18:43 EST
/etc/init.d/NetworkManager starts the "bind" service.
When NetworkManager was using dhcdbd (pre-F8), it made sense to have named
started as resolv.conf was always pointing to the localhost named instance.
Now that dhcdbd is gone, NetworkManager should not need named.
BTW, I think that dhcdbd was a better approach, as the local named instance
would try to query the DHCP-provided DNS server and was falling back to
resolving from the root servers if the (DHCP-provided) forwarders were not
Any chance to have dhcdbd back?
*** Bug 390191 has been marked as a duplicate of this bug. ***
NetworkManager-0.7.0-0.6.6.svn3138.fc8 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update NetworkManager'
NetworkManager-0.7.0-0.6.6.svn3138.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.