Bug 125781

Summary: system-config-bind and named does not find same zone file
Product: [Fedora] Fedora Reporter: Jørgen Nørgaard <jnp>
Component: bindAssignee: Jason Vas Dias <jvdias>
Status: CLOSED CURRENTRELEASE QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 2   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: bind-9.2.4rc6-4 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-08-03 20:57:48 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 Jørgen Nørgaard 2004-06-11 13:00:11 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/125.2 (KHTML, like Gecko) Safari/125.8

Description of problem:
For system-config-bind to find the zone file 


/var/named/chroot/etc/named.conf must be like:

zone "lab" { 
	type master;
#	file "/var/named/lab.zone";
	file "lab.zone";
};


But for named to find the zone file it must be:
zone "lab" { 
	type master;
	file "/var/named/lab.zone";
#	file "lab.zone";
};

Now system-config-bind cannot read the file ...

Both files generated from scratch by system-config-bind.




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


How reproducible:
Always

Steps to Reproduce:
1. create a new zone
2. add hosts
3. (re-)start named


    

Actual Results:  With the system-config-bind named.conf this error is in /var/log/messages:

..  named[5595]: zone lab/IN: loading master file lab.zone: file not found


Additional info:
Comment 1 Jason Vas Dias 2004-08-03 20:57:48 UTC 
This is now fixed.
You wrote:
> But for named to find the zone file it must be:
> zone "lab" { 
>	type master;
>	file "/var/named/lab.zone";
>#	file "lab.zone";
>};
Not so for bind-9.2.4rc6-+ - it can now just be 'lab.zone'.