In-Reply-To: <rt-4.4.1-3770-1499175609-609.44790-0-0@isc.org>
Content-Disposition: inline
Content-Type: text/plain; charset="utf-8"
X-RT-Interface: Web
References: <rt-4.2.8-78137-1488400667-1945.0-0-0@isc.org>
 <RT-Ticket-44790@isc.org> <rt-4.4.1-3770-1499175609-609.44790-0-0@isc.org>
Message-ID: <rt-4.4.1-90590-1501140691-147.44790-0-0@isc.org>
X-RT-Original-Encoding: utf-8
Content-Transfer-Encoding: binary
MIME-Version: 1.0
X-Mailer: MIME-tools 5.508 (Entity 5.508)
RT-Send-CC:
Content-Length: 835

On Tue Jul 04 03:40:09 2017, stephen wrote:
> Reviewed the documentation and tests for commit
> 8ce30b9b86d0fd11d26ba2fb0037ea5c29832eef. (Note: the code has NOT been
> reviewed.)
> 
> Documentation
> ===
> There is nothing in the ARM about "rndc serve-stale" command.  In
> particular, what does "serve-stale reset" command do?

The arm includes the rndc man page.  That said I've added a
reference to it.

> In the ARM, the documentation for stale-answer-ttl should note that
> max-stale-ttl has to also be set to enable the serving of stale
> answers.

added.

> max-stale-ttl does not seem the right name for this option: to my
> mind, it suggests that the value is the maximum value of a stale
> record's TTL.  max-stale-retention or max-stale-retain might be a
> better name.

It's consistent with max-cache-ttl, max-ncache-ttl.