ERROR : - writeable file 'data/udalgurijudiciarygov.hosts': already in use: /etc/nicnet2007.govdomain:15424 - loading configuration: failure

[Reindl Harald]

Am 03.08.2015 um 16:50 schrieb Heiko Richter:
> Am 03.08.2015 um 08:08 schrieb Mukund Sivaraman:
>> Hi Prakash
>>
>> On Mon, Aug 03, 2015 at 10:14:50AM +0530, prakash wrote:
>>> Aug  3 09:59:34 govindnsvm named[7436]: /etc/nicnet2007.govdomain:15424: writeable file 'data/udalgurijudiciarygov.hosts': already in use: /etc/nicnet2007.govdomain:15424
>>> Aug  3 09:59:34 govindnsvm named[7436]: /etc/nicnet2007.govdomain:15431: writeable file 'data/bodolandgov.hosts': already in use: /etc/nicnet2007.govdomain:15431
>>> Aug  3 09:59:34 govindnsvm named[7436]: /etc/nicnet2007.govdomain:15445: writeable file 'data/cexhyd2gov.hosts': already in use: /etc/nicnet2007.govdomain:15445
>>> Aug  3 09:59:34 govindnsvm named[7436]: /etc/nicnet2007.govdomain:15452: writeable file 'data/bmcsagaredu.hosts': already in use: /etc/nicnet2007.govdomain:15452
>>> Aug  3 09:59:34 govindnsvm named[7436]: /etc/nicnet2007.govdomain:15459: writeable file 'data/crckozhikodegov.hosts': already in use: /etc/nicnet2007.govdomain:15459
>>> Aug  3 09:59:34 govindnsvm named[7436]: /etc/nicnet2007.govdomain:15466: writeable file 'data/wblcgov.hosts': already in use: /etc/nicnet2007.govdomain:15466
>>> Aug  3 09:59:34 govindnsvm named[7436]: /etc/nicnet2007.govdomain:15473: writeable file 'data/precursorsncbgov.hosts': already in use: /etc/nicnet2007.govdomain:15473
>>> Aug  3 09:59:34 govindnsvm named[7436]: /etc/nicnet2007.govdomain:15480: writeable file 'data/icggov.hosts': already in use: /etc/nicnet2007.govdomain:15480
>>> Aug  3 09:59:34 govindnsvm named[7436]: loading configuration: failure
>>> Aug  3 09:59:34 govindnsvm named[7436]: exiting (due to fatal error)
>>
>> See if you have used these "data/*.host" as values with the "file"
>> option multiple times in your named configuration. It may be that you
>> have included a config snippet multiple times.
>>
>
> Why use the "file" option at all on a slave?
>
> Of course it is possible, but why should one force the file name of a
> slave zone? That configuration option is just needed on the master.
>
> Bind will assign a filename for your slave zone on its own and you can
> be sure it will not assign the same name twice....

and will it remove the file also automatically if the zone no longer 
exists in the config?

our backends as example are naming the zones domain.tld.dns on master 
and slave and if we remove a domain the files on both are deleted too 
before reload named

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20150803/ddb47e7e/attachment.bin>