Return-Path: Date: Wed, 3 Jan 2018 22:16:02 +0000 User-Agent: Mutt/1.5.23 (2014-03-12) Content-Transfer-Encoding: 8bit CC: To: "Mark Andrews via RT" From: "Evan Hunt" References: <3E18C1A0C550C44DA156DA5DA8ECCC6AA2D6EA43@NICS-EXCH2.sbg.nic.at> <30884B13-9973-4DBF-871F-E4AD21F4EA8C@isc.org> From each@isc.org Wed Jan 3 22:16:03 2018 MIME-Version: 1.0 X-RT-Interface: Email X-RT-Incoming-Encryption: Not encrypted Subject: Re: [ISC-Bugs #46875] rndc zonestatus type is wrong for bump-in-the-wire signed zone In-Reply-To: Message-ID: <20180103221602.GA73325@isc.org> X-RT-Original-Encoding: utf-8 Content-Disposition: inline Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by bugs.isc.org (Postfix) with ESMTPS id 661C4D78B0D for ; Wed, 3 Jan 2018 22:16:03 +0000 (UTC) Received: by bikeshed.isc.org (Postfix, from userid 10292) id CCF0D216C1C; Wed, 3 Jan 2018 22:16:02 +0000 (UTC) X-Original-To: bind9-public@bugs.isc.org Delivered-To: bind9-public@bugs.isc.org content-type: text/plain; charset="utf-8" RT-Message-ID: Content-Length: 702 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.