From owner-freebsd-current@FreeBSD.ORG  Mon Sep  1 14:12:24 2008
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 3396B106566B
	for <freebsd-current@freebsd.org>; Mon,  1 Sep 2008 14:12:24 +0000 (UTC)
	(envelope-from alex-goncharov@comcast.net)
Received: from QMTA06.emeryville.ca.mail.comcast.net
	(qmta06.emeryville.ca.mail.comcast.net [76.96.30.56])
	by mx1.freebsd.org (Postfix) with ESMTP id 1A4E58FC0C
	for <freebsd-current@freebsd.org>; Mon,  1 Sep 2008 14:12:24 +0000 (UTC)
	(envelope-from alex-goncharov@comcast.net)
Received: from OMTA01.emeryville.ca.mail.comcast.net ([76.96.30.11])
	by QMTA06.emeryville.ca.mail.comcast.net with comcast
	id 9PPt1a0040EPchoA6S2Qka; Mon, 01 Sep 2008 14:02:24 +0000
Received: from daland.home ([24.61.21.4])
	by OMTA01.emeryville.ca.mail.comcast.net with comcast
	id 9S2N1a00805H7zL8MS2Pk1; Mon, 01 Sep 2008 14:02:24 +0000
X-Authority-Analysis: v=1.0 c=1 a=aVV7_ef_2ZQA:10 a=y3Be58pVqgkA:10
	a=rITDv7nW5hcA:10 a=tBTIeuz21jnuXfyD9oYA:9
	a=miZ-xwcqITgsGs0uY28W0JRVJZ8A:4
	a=si9q_4b84H0A:10 a=mhQ4J5QMNLoA:10
Received: from algo by daland.home with local (Exim 4.69 (FreeBSD))
	(envelope-from <algo@daland.home>)
	id 1Ka9z3-0009PA-Rw; Mon, 01 Sep 2008 10:02:21 -0400
From: Alex Goncharov <alex-goncharov@comcast.net>
To: Stefan Bethke <stb@lassitu.de>
In-reply-to: <9B5F3198-4C3E-4FDE-B9BC-2C67B0B82CEC@lassitu.de> (message from
	Stefan Bethke on Mon, 1 Sep 2008 15:31:37 +0200)
References: <E1Ka8cJ-000GgI-Um@daland.home>
	<9B5F3198-4C3E-4FDE-B9BC-2C67B0B82CEC@lassitu.de>
Message-Id: <E1Ka9z3-0009PA-Rw@daland.home>
Sender: Alex Goncharov <alex-goncharov@comcast.net>
Date: Mon, 01 Sep 2008 10:02:21 -0400
Cc: freebsd-current@freebsd.org, alex-goncharov@comcast.net
Subject: Re: named mystery -- error: dumping master file:
	master/tmp-wTjhUzoix6
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Alex Goncharov <alex-goncharov@comcast.net>
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Sep 2008 14:12:24 -0000

,--- You/Stefan (Mon, 1 Sep 2008 15:31:37 +0200) ----*
| Why is named trying to dump a master zone? The root ownership is  
| intentional: since named is only serving these zones, not receiving or  
| updating them, the files are not writeable by the bind user.

Sorry, why can't a master zone be updatable?

How about rndc?  How about making entries per DHCP daemon requests?

Is there a standard statement that a master zone can't be dynamically
updated?

-- Alex -- alex-goncharov@comcast.net --