3 Apr
2011
3 Apr
'11
2:39 p.m.
Nevermind, that doesn't work if the zone doesn't change.
Shame bind is so impenetrable, if there was a simple way of asking it what it's
internal expire counter had you could do this quite easily.
On 3 Apr 2011, at 15:26, David Leadbeater wrote:
On 3 Apr 2011, at 01:56, Andy Smith wrote:
The problem is I can't think of a way to
check that AXFR works
without doing an AXFR. :) Can anyone else?
1. Ask your server (probably just your primary) and the customer's server for the
SOA.
2. If the serial on the customer's server is newer than yours record this as the
first time that serial was seen for this domain in a DB (SQLite probably simplest?).
3. If your server still isn't up-to-date after a suitable timeframe (refresh period
of the SOA, or less if you trust/expect notifies to be working) raise an alert.
[I know you use PowerDNS in places, another idea along similar lines could be to change
the PowerDNS schema to record this extra info and alert via that. The usual concerns about
monitoring becoming too closely tied to the app apply here though.]
David
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users