Issue in calling same zone in more than one VIEW

Cathy Almond cathya at
Fri May 29 10:25:48 UTC 2015

On 29/05/2015 10:39, Gaurav Kansal wrote:
> Thanks for information.
> Is there any other way by which I can define the zone (which are same for
> all views) outside the view or anything else by which I don't need to
> replicate the file for all the views.
> Regards,
> Gaurav Kansal
> -----Original Message-----
> From: Niall O'Reilly [mailto:niall.oreilly at] 
> Sent: Friday, May 29, 2015 1:48 PM
> To: Gaurav Kansal
> Cc: bind-users at
> Subject: Re: Issue in calling same zone in more than one VIEW
> On Fri, 29 May 2015 08:23:55 +0100,
> Gaurav Kansal wrote:
>> Dear Team,
>> I am running BIND 9.10.2 version on CentOS and running roughly 500 
>> domains and for most of them I am a slave server.
>> In few of them, I have different zone file based on Internal and 
>> External view.
>> And for rest of them, I am using a single file for both the View.
>> This configuration was working fine till BIND version 9.9.5
>   As I understand, this configuration was never supported.
>   Each instance (view) of a slave server needs a private file in which
>   to write zone data transferred from the master.  Having multiple
>   instances use the same file means that they may over-write each
>   other's work.  Managing this contention was never a design feature.
>> but
>> yesterday I updated to 9.10.2 and I am facing the following error.
>> May 29 12:43:58 NKN-IPV6-DNS named[17727]:
>> /var/named/zonedata/ writeable file
>> 'govdomains/': already in use:
>> /var/named/zonedata/
>   The new version now gives an error message in case you use this
>   kind of unsupported configuration.
>> This is happening because I am calling same zone file in both view.
>> Please help me out what I should do for getting rid of this issue.
>   You need to use as many copies of each zone file as you have views
>   needing to write to it.
>   Best regards,
>   Niall O'Reilly

>From 9.10.0 there is a new zone type 'in-view'.  From the release notes:

The new "in-view" zone option allows zone data to be shared between
views, so that multiple views can serve the same zones authoritatively
without storing multiple copies in memory. [RT #32968]

I think this will do what you want (apologies for the scant
documentation about it)


More information about the bind-users mailing list