Warren,
I wrote a tool to do this a while back --
http://code.google.com/p/dns-slave-expire-checker/
Cool stuff and very useful. I took it for a tiny spin, and here are my
EUR 0.02 :)
1. Doesn't seem to grok all RRtypes in slave zones, due probably to
missing functionality of dnspython;
On May 21 2012, 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.
On 21.05.12
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
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
-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
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
On May 21 2012, 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.
Do you
On May 21, 2012, at 2:02 PM, Mike Hoskins wrote:
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
Thanks! I'll try the various monitoring options... I don't have
try-tcp-refresh no, so I'm afraid that doesn't explain it either...
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing
While not a help at the moment, BIND 9.10 has rndc zonestatus which
will report when the zone is due expire.
Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org
___
10 matches
Mail list logo