Bug 381571

Summary:	NetworkManager starts bind needlessly
Product:	[Fedora] Fedora	Reporter:	Philippe Troin <phil>
Component:	NetworkManager	Assignee:	Dan Williams <dcbw>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	8	CC:	dcbw, ndbecker2, wtogami
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	0.7.0-0.6.6.svn3138.fc8	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-01-07 01:18:43 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Philippe Troin 2007-11-14 05:24:12 UTC

/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
responsive.
Any chance to have dhcdbd back?

Phil.

Comment 1 Dan Williams 2007-11-26 16:18:39 UTC

*** Bug 390191 has been marked as a duplicate of this bug. ***

Comment 2 Fedora Update System 2007-12-07 21:34:26 UTC

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'

Comment 3 Fedora Update System 2008-01-07 01:18:34 UTC

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.