Bug 246373

Summary:	bind-9.4.1-6.1.fc7 breaks caching-nameserver
Product:	[Fedora] Fedora	Reporter:	David Juran <djuran>
Component:	bind	Assignee:	Adam Tkac <atkac>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7	CC:	ovasik
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-07-08 18:12:59 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 David Juran 2007-07-01 08:54:04 UTC

Description of problem:
After updating to bind-9.4.1-6.1.fc7, my caching nameserver broke.

[david@localhost ~]$ sudo /sbin/service named start
Starting named: 
Error in named configuration:
zone localdomain/IN: loading from master file localdomain.zone failed: file not
found
_default/localdomain/IN: file not found
zone localhost/IN: loading from master file localhost.zone failed: file not found
_default/localhost/IN: file not found
zone 0.0.127.in-addr.arpa/IN: loading from master file named.local failed: file
not found
_default/0.0.127.in-addr.arpa/IN: file not found
zone 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN:
loading from master file named.ip6.local failed: file not found
_default/0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN:
file not found
zone 255.in-addr.arpa/IN: loading from master file named.broadcast failed: file
not found
_default/255.in-addr.arpa/IN: file not found
zone 0.in-addr.arpa/IN: loading from master file named.zero failed: file not found
_default/0.in-addr.arpa/IN: file not found



Version-Release number of selected component (if applicable):
bind-9.4.1-6.1.fc7

How reproducible:
Every time

Steps to Reproduce:
1. service named start

Comment 1 Adam Tkac 2007-07-02 11:16:52 UTC

I don't believe. That zones aren't loaded in default configuration. Please make
sure that you don't using /etc/named.conf and please attach complete log of
named start and you configfiles.

Adam

Comment 2 David Juran 2007-07-08 18:12:59 UTC

You're right, I was using /etc/named.conf, removing it solves the problem.
 Not sure where it came from though, both my computers that had been updated
from FC-6 to F-7 ended up with this faulty /etc/named.conf around the same time
that I applied the bind-9.4.1-6.1.fc7 update. Anyway, closing this as NOTABUG,
sorry for the hassle.