Mark,
Thanks. I found where this was discussed here previously (Jan. 2003);
apologies for not being thorough.
- David Covey
Deophysical Institute, University of Alaska Fairbanks
> To: David Covey
> Cc: bind-us...@isc.org
> From: Mark Andrews
> Subject: Re: nsupdate and views
> Date
Use different TSIG keys to direct the UPDATE request to the correct view.
In message <5508dd86.kc1mmon8e03wtkto%david.co...@gi.alaska.edu>, David Covey w
rites:
> Hello all,
> I don't quite see how to dynamically manage multiple views of a
> zone. Specifically I have a zone name with both 'in
Hello all,
I don't quite see how to dynamically manage multiple views of a
zone. Specifically I have a zone name with both 'internal' and 'external'
views that I'd like to manage with the nsupdate command. Is there a
way to specify the zone+view using nsupdate?
- David Covey
Geophysical In
Referencing the same writable file in multiple places in named can:
* lead to corrupted journals
* the wrong zone content being published in the wrong view
* named not being able to serve zone content when restarted when the
master is down
* content not showing up in a timely manner
* extra zo
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 true.
Of course, sorry.
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" option. Moreover, these two definitions must be in different
>> fil
On 17.03.2015 18:05, Lightner, Jeff wrote:
> 4.x would be quite ancient. Where are you getting those version
> numbers? You should be using 9.x these days so I suspect the BIND
> version isn't what you think it is.Is it possible the version
> you're reporting is you OS rather than your BI
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" option. Moreover, these two definitions must be in different
> files, as I have to include one in first view, and
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 true.
> With 4.6 I had the following config:
>
> named.conf:
>
> vi
4.x would be quite ancient. Where are you getting those version numbers?
You should be using 9.x these days so I suspect the BIND version isn't what you
think it is.Is it possible the version you're reporting is you OS rather
than your BIND?
What is reported when you run "named -v"?
An
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
11 matches
Mail list logo
