-----Original Message----- From: Barry Margolin <bar...@alum.mit.edu> Organization: A noiseless patient Spider Date: Monday, May 21, 2012 12:59 PM To: <comp-protocols-dns-b...@isc.org> Subject: Re: Checking for zone expiration?
>In article <mailman.837.1337627794.63724.bind-us...@lists.isc.org>, > Alan Batie <a...@peak.org> wrote: > >> We had a rather key zone mysteriously expire on a slave this morning - >> the log files show a transfer a couple weeks ago, but it hadn't been >> updated so there was no reason for one since and there were no log >> entries about failed connection attempts. I was wondering if there's a >> way to check the remaining time on a zone for monitoring? If you fetch >> the SOA, you get the full ttl, for obvious reasons, not the server's >> timer... > >Check the modification time of the zone file on the slave server, that's >when it was last refreshed. > >-- >Barry Margolin >Arlington, MA as usual there is more than one way to skin a cat... another network-based way that doesn't involve local mtime checks would be querying the master soa from your monitoring host, and then hitting each slave on port 8080 (or whatever) via statistics-channels (if you enable it) as mentioned earlier on the list. the statistics view returns xml you can parse which includes the zones and serials for each zone in each view on the slave. _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
