Date: Wed, 26 Jan 2000 08:49:32 -0800 From: "Kevin Oberman" <oberman@es.net> To: Veaceslav Revutchi <sl@dnt.md> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: No default TTL & CNAME and OTHER data error Message-ID: <200001261649.IAA14963@ptavv.es.net> In-Reply-To: Your message of "Wed, 26 Jan 2000 11:56:58 %2B0200." <Pine.BSF.4.10.10001261143410.48097-100000@zeus.dnt.md>
next in thread | previous in thread | raw e-mail | index | archive | help
8.2 releases of BIND implement new RFCs which mandate that the minimum TTL in the SOA really be used as minimum TTL. This is very significant for negative caching. As a result, this value should not be used for the default TTL and a new directive to specify the default has been added. You probably want to do the following: 1. Insert the line "$TTL 1D" before the SOA in every zone file. 2. Change the minimum TTL in the SOA to a value more appropriate to a real minimum, say 600 or 900. Once this is done, the $TTL will be used as default for all records not containing an explicit TTL and the SOA minimum TTL value will be used as the TTL for negative entries and as the actual minimum TTL. In previous versions of BIND these (true minimum and negative cache TTLs) were hard coded. Minimum TTL does not preclude setting the TTL for one or more records to zero. This means that the server should never cache the records. But a non-zero value below minimum will be replaced by the minimum. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200001261649.IAA14963>