How to check slave zone freshness

Warren Kumari warren at
Mon Feb 8 13:59:07 UTC 2016

The standard, compatible way to do this is simply to do a lookup for the
SOA record and make sure that the serial number matches what you expect it
to be / what is on the master. I'm not sure what monitoring tool you are
using (or if you are writing your own), but most standard monitoring tools
have such a script already written - e.g:

I believe that BIND also updates the mtime on the zone file when it does
the check (not only when something changes):
root at eric:/etc/namedb/slave# date
Mon Feb  8 08:36:58 EST 2016
root at eric:/etc/namedb/slave# ls -al*
-rw-r--r-- 1 named named  714 Feb  8 03:51
-rw-r--r-- 1 named named 1236 Feb  8 03:51
root at eric:/etc/namedb/slave#

So, you should be able to just run 'ls' and see if the 'mtime' is larger
than you expect...


On Mon, Feb 8, 2016 at 5:40 AM Klaus Darilion <klaus.mailinglists at>

> Hi!
> I want to monitor the freshness of my slaves zones. Is it somehow
> possible to extract the status of slave-zones from bind?
> Thanks
> Klaus
> _______________________________________________
> Please visit to
> unsubscribe from this list
> bind-users mailing list
> bind-users at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the bind-users mailing list