Generally Accepted Values

Michael Kjorling michael at
Fri Oct 5 10:38:07 UTC 2001

Hash: SHA1

A question that arose when I was reading this document more carefully:

It specifies setting the SOA MINTTL to 2 days (172800). However, it is
also mentioned that this value is used as the default TTL - which is
not the BIND 9 way. I have TTLs specified for all RRs anyway (mostly
through $TTL directives, but some overrides those as well) - and that
we are going through a transition period to using the MINTTL as a
negative caching TTL.

My question is - what would be a reasonable negative caching TTL for
zones that do not change very often? As far as I have understood
NXDOMAIN responses are only given if the authorative server does not
find the requested resource record, so the possibility of any other
cause for a NXDOMAIN response can probably be ruled out.

I have a few zones that change very rarely - I have been working on
them lately but last time I made any significant changes was when one
of my secondaries was down for an extended period of time.

Any suggestions as to what value to use?

Michael Kjörling

On Oct 3 2001 12:42 +0100, James Raftery wrote:

> On Mon, Oct 01, 2001 at 11:46:30AM -0700, Chris Parker wrote:
> > What are the generally accepted values for Refresh, Retry, Expire, and TTL
> > for a domain that is not expected to change in the foreseeable future?
> should be a reasonable
> starting point.
> Regards,
> james

- -- 
Michael Kjörling  --  Programmer/Network administrator  ^..^
PGP: 95f1 074d 336d f8f0 f297 6a5b 2aa3 7bfd 8a70 e33e   \/
Internet: michael at -- FidoNet: 2:204/254.4

"There is something to be said about not trying to be glamorous
and popular and cool. Just be real -- and life will be real."
(Joyce Sequichie Hifler, September 13 2001)
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For my PGP key:


More information about the bind-users mailing list