On 06/24/2011 10:47 PM, Brian J. Murrell wrote:
On 11-06-24 03:19 PM, David Sparro wrote:
Do you have control of the update process.
Sure.
You could potentially send
and update to both views (in other words, send two updates).
How do I, with nsupdate, specify which view's zone I want to u
On 11-06-24 03:19 PM, David Sparro wrote:
>
> Do you have control of the update process.
Sure.
> You could potentially send
> and update to both views (in other words, send two updates).
How do I, with nsupdate, specify which view's zone I want to update?
> I think
> you'd need separate zone f
On 6/24/2011 2:51 PM, Brian J. Murrell wrote:
The data really does need to be quite in sync though. I'm not sure a
period of less than a second or two is going to be acceptable.:-(
Do you have control of the update process. You could potentially send
and update to both views (in other words,
On 11-06-24 01:47 PM, Evan Hunt wrote:
>
> Do the internal and external versions *both* need to be dynamic?
No, only the internal in fact.
> I'd expect it to work okay if you had only one of them dynamic, and
> sent periodic reload commands to the other one.
Yeah. I got the master/slave appro
> But reload doesn't work for dynamic zones:
Do the internal and external versions *both* need to be dynamic?
I'd expect it to work okay if you had only one of them dynamic, and
sent periodic reload commands to the other one.
The master/slave approach really works better, though. Something like
On 11-06-24 12:39 PM, Evan Hunt wrote:
>
> You can specify the view in the reload command:
>
> $ rndc reload example.com in external
But reload doesn't work for dynamic zones:
# rndc reload rbl.interlinx.bc.ca in greatunwashed
rndc: 'reload' failed: dynamic zone
and since I want the sa
> A. I guess I had not considered how BIND handles "views" and that
> it's done with a separate process per view. But I only have one named
> process, so I suppose it's threading for each view.
No, the views will all share the same process and thread(s), but they are
separate chunks of memor
On 06/24/11 09:21, Brian J. Murrell wrote:
On 11-06-24 09:57 AM, Lyle Giese wrote:
It's expected behavior in a way.
Given your explanation, indeed. :-)
You are probably making this change in
the internal view and the internal named process knows about the change
and reloads the zone.
The
On 11-06-24 09:57 AM, Lyle Giese wrote:
>
> It's expected behavior in a way.
Given your explanation, indeed. :-)
> You are probably making this change in
> the internal view and the internal named process knows about the change
> and reloads the zone.
>
> The external view's process is unaware
On 24/06/11 14:22, Brian J. Murrell wrote:
I am using BIND 9.7.2-P2.
I have two views, one "internal" and one for "external" queries. In
both of those views I have some zones which are common so I put them
into their own file "zones.common" and include that file in both of the
views.
The probl
On 06/24/11 08:22, Brian J. Murrell wrote:
I am using BIND 9.7.2-P2.
I have two views, one "internal" and one for "external" queries. In
both of those views I have some zones which are common so I put them
into their own file "zones.common" and include that file in both of the
views.
The probl
I am using BIND 9.7.2-P2.
I have two views, one "internal" and one for "external" queries. In
both of those views I have some zones which are common so I put them
into their own file "zones.common" and include that file in both of the
views.
The problem I am having is that when I make a dynamic
12 matches
Mail list logo
