> -----Ursprüngliche Nachricht-----
> Von: Evan Hunt via RT [mailto:bind9-public@isc.org]
> Gesendet: Mittwoch, 3. Jänner 2018 23:16
> An: Klaus Darilion <klaus.darilion@nic.at>
> Betreff: Re: [ISC-Bugs #46875] rndc zonestatus type is wrong for bump-
> in-the-wire signed zone
> 
> On Wed, Jan 03, 2018 at 10:08:32PM +0000, Mark Andrews via RT wrote:
> > > What's there is okay, and can be committed, but it occurs to me it's
> > > incomplete.  We have expiry and refresh timers being reported only
> for
> > > the signed zone, but if the raw zone is type slave then we should
> have it
> > > reported for both, the way we currently do with serial numbers.
> >
> > They don’t make sense for the signed zone.  s/zone/mayberaw/
> 
> That was my first thought, but I think those values are actually
> potentially meaningful (even if only in an error condition) for
> the signed zone too.
> 
> We could switch to reporting from mayberaw in the existing code,
> but change to a more detailed output format in 9.13.


Some comment from a user: I actually found this issue as I was interested to find out the freshness-status of a slave zone - regardless if the zone is unsigned or "bump-in-the-wire" signed, and regardless if the zone is further slaved or not.

Unfortunately the freshness status is missing total. With freshness I mean:
- was the last SOA-check against the master successfull (at least 1 master if there are multiple masters)
- is the slave's serial identical to the master's serial?
- was the last XFR try successful?

I want to know if there is a problem between master and slave bevore noticing that the zone expired. And this is currently not exposed to "zonestatus". Watching the logfile is cumbersome and may reports false positive if there are transitional communication problems.

Shall I open a "feature request"?

Thanks
Klaus