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: https://exchange.nagios.org/directory/Plugins/Network-Protocols/DNS/checkexpire/details
I believe that BIND also updates the mtime on the zone file when it does the check (not only when something changes): root@eric:/etc/namedb/slave# date Mon Feb 8 08:36:58 EST 2016 root@eric:/etc/namedb/slave# ls -al superficialinjurymonkey.com* -rw-r--r-- 1 named named 714 Feb 8 03:51 superficialinjurymonkey.com -rw-r--r-- 1 named named 1236 Feb 8 03:51 superficialinjurymonkey.com.jnl root@eric:/etc/namedb/slave# So, you should be able to just run 'ls' and see if the 'mtime' is larger than you expect... W On Mon, Feb 8, 2016 at 5:40 AM Klaus Darilion <klaus.mailingli...@pernau.at> wrote: > 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 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
