detect if zone/s is frozen

Kevin Darcy kcd at chrysler.com
Tue Sep 3 22:15:10 UTC 2013


On 9/3/2013 5:24 PM, Mike Hoskins (michoski) wrote:
> -----Original Message-----
>
> From: /dev/rob0 <rob0 at gmx.co.uk>
> Organization: RTFM
> Reply-To: "bind-users at lists.isc.org" <bind-users at lists.isc.org>
> Date: Tuesday, September 3, 2013 5:17 PM
> To: "bind-users at lists.isc.org" <bind-users at lists.isc.org>
> Subject: Re: detect if zone/s is frozen
>
>> On Tue, Sep 03, 2013 at 12:31:08PM -0700, Justin T Pryzby wrote:
>>> Is there a nice way to tell if any zone is frozen (or a
>>> specific zone)?  I'm hoping to implement a nagios check, since
>>> I have several times gotten distracted while making an update,
>>> and forgot to "thaw"ed the zone until something odd happens
>>> later on.
>> I would suggest that if you're making much use of rndc freeze, YDIW.
>> Consider using nsupdate(8) to make your changes.
> True, but I just setup two new networks where the tenants wanted exactly
> this capability...so use cases exist.
So put a wrapper around "rndc", tell them the zone files are in a 
different directory than they really are, and invoke "nsupdate" behind 
the scenes, to make the actual changes. They'll *think* they're doing 
freeze/edit/thaw, but in actuality the mechanism will be smarter than 
that :-)

         - Kevin


More information about the bind-users mailing list