bind restart needed to reflect changes to dynamic zone in multipleviews

[Lightner, Jeff]

I wonder if pointing to different file "names" with one being a symbolic
link to the other would work? That way you'd only have to create and
update the one file but the transfer would transfer two separate files.

-----Original Message-----
From: bind-users-bounces+jlightner=water.com at lists.isc.org
[mailto:bind-users-bounces+jlightner=water.com at lists.isc.org] On Behalf
Of Brian J. Murrell
Sent: Friday, June 24, 2011 10:21 AM
To: bind-users at isc.org
Subject: Re: bind restart needed to reflect changes to dynamic zone in
multipleviews

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 of the change and does not
reload.

Ahhhh.  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.

> 1) You could send a periodic rndc reload to the external view process.

Except that I only have the one process.  Any thoughts on how to do this
in such a case?

> 2) Since this appears to be an rbl zone, use rbldnsd instead of named
to
> serve this zone.

Yeah, I suppose I could.  It would solve this specific use case, but I
don't know that this RBL zone is the extent of this problem.  I'd have
to examine further where there are zones shared by multiple views.  I'm
guessing though that rbldnsd doesn't support remote update, yes?  That
would be limiting for my purposes here.

Cheers,
b.
 
Proud partner. Susan G. Komen for the Cure.
 
Please consider our environment before printing this e-mail or attachments.
----------------------------------
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you.
----------------------------------