Bug 195784 - NM starts named but doesn't use it
Summary: NM starts named but doesn't use it
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: bind
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Adam Tkac
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-06-17 18:48 UTC by Chris Adams
Modified: 2013-04-30 23:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-05-30 10:05:44 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Chris Adams 2006-06-17 18:48:06 UTC 
The NetworkManager init script starts named but doesn't appear to use it.  When
connecting to a network, /etc/resolv.conf points at the DHCP assigned name
servers (not the local named).
Comment 1 Dan Williams 2006-07-09 23:47:42 UTC 
It appears that named doesn't get started with the -D option by default to
enable dbus.  Jason?
Comment 2 Dan Williams 2006-07-09 23:48:11 UTC 
It appears that named doesn't get started with the -D option by default to
enable dbus.  Jason?
Comment 3 Jason Vas Dias 2006-07-19 21:45:30 UTC 
This is now fixed with bind-9.3.2-30.fc6, and with bind-9.3.2-22.fc5, now being
released to FC-5 updates/testing.
Now, if the NetworkManager service is enabled in any runlevel, the named 
initscript will ensure that the named options contain -D.
Comment 4 Fedora Update System 2006-07-22 18:59:38 UTC 
bind-9.3.2-22.fc5 has been pushed for fc5, which should resolve this issue.  If these problems are still present in this version, then please make note of it in this bug report.
Comment 5 Adam Tkac 2007-05-30 10:05:44 UTC 
Looks like fixed. If still exists, please reopen.

Regards, Adam
Note You need to log in before you can comment on or make changes to this bug.