On May 21, 2012, at 3:16 PM, Alan Batie 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?
Why yes, yes there is… I wrote a tool to do this a while back -- http://code.google.com/p/dns-slave-expire-checker/ Basically, it runs on the slave and checks to see if the MTIME on the file is getting close to the TTL. If so it will generate a warning, if the zone expires it will generate an error. I don't think I ever mentioned it's existence to anyone, so YMMV, etc. Lemme know if it sucks/ has bugs / causes male pattern baldness and I'll try take care of that… W > If you fetch > the SOA, you get the full ttl, for obvious reasons, not the server's > timer... > > _______________________________________________ > 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 > _______________________________________________ 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
