On 18.03.2015 11:56, Matus UHLAR - fantomas wrote:
> On 18.03.15 11:48, Constantin Stefanov wrote:
>> But in fact the configuration with only one writable file referenced
>> several times is suported now. If I write:
>>
>> view "view1" {
>> zone &qu
I see why it may lead to problems.
But in fact the configuration with only one writable file referenced
several times is suported now. If I write:
view "view1" {
zone "aaa.exampe.org" {
masters {IP;};
file "slave/aaa.exmaple.org";
};
};
view "view2
On 17.03.2015 18:32, /dev/rob0 wrote:
> On Tue, Mar 17, 2015 at 05:36:57PM +0300, Constantin Stefanov wrote:
>> After upgrading from BIND 4.6 to 4.10.2, named requires that
>> different slave zone have separate file for cache.
>
> Surely you mean s/4/9/g, and yes, this is t
On 17.03.2015 19:34, Tony Finch wrote:
> Constantin Stefanov wrote:
>>
>> I found 'in-view' option, but again it requires two definitions for
>> every zone: one with "file" and "masters" directives, and another with
>> "in-view
uestion is - how to make the config simple, as was available before
upgrade.
>
> -Original Message- From: bind-users-boun...@lists.isc.org
> [mailto:bind-users-boun...@lists.isc.org] On Behalf Of Constantin
> Stefanov Sent: Tuesday, March 17, 2015 10:37 AM To:
> bind-users@l
Hello.
After upgrading from BIND 4.6 to 4.10.2, named requires that different
slave zone have separate file for cache.
With 4.6 I had the following config:
named.conf:
view "internal" {
match /* match condition */;
include "common.zones";
};
view "external" {
match /* m
6 matches
Mail list logo
