Bug 123282 - named.conf in the wrong place when using chroot environment
Summary: named.conf in the wrong place when using chroot environment
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: bind
Version: 2
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jason Vas Dias
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-05-15 18:01 UTC by Joerg Sippel
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version: bind-9.2.4rc6-3
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-08-04 14:29:07 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Joerg Sippel 2004-05-15 18:01:57 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; i-
NavFourF; .NET CLR 1.1.4322)

Description of problem:
When installed Fedora Core2 Test3 the named doesn't start correctly 
because the configuration file is /etc/named.conf but the process is 
using /var/named/chroot/etc/named.conf which is available but empty.

Version-Release number of selected component (if applicable):
bind-9.2.3-13

Actual Results:  The nameserver is unusable because of the missing 
configuration

Additional info:
Comment 1 Joerg Sippel 2004-05-19 14:45:18 UTC 
this issue is also in Fedora Core 2 final release
Comment 2 Arnaud MOURONVAL 2004-05-31 19:10:44 UTC 
Temporary workaround : comment the variable definition for CHROOT in
/etc/sysconfig/named
Comment 3 Jason Vas Dias 2004-08-04 14:29:07 UTC 
fixed in bind-9.2.4rc6-3
Note You need to log in before you can comment on or make changes to this bug.