Need help debugging negative caching

[Mark_Andrews at isc.org]

> 
> Mark_Andrews at isc.org wrote in message news:<akoqqr$29k8$1 at isrv4.isc.org>...
> > 
> > 	The fact that it is using it as the default TTL doesn't mean that
> > 	it can't emit negative answers with the TTL you want.
> > 
> > 	Just set the MINIMUM field to the TTL you want on the negative
> > 	answers.  Use this TTL on the SOA.  Set explict TTLs on all the
> > 	other records to the old MINIMUM value.
> > 
> > 	Setting the MINIMUM field will allow slaves that talk RFC 2308 to
> > 	do the right thing.  Setting the SOA TTL will get the non RFC 2308
> > 	server to hand out the right TTL.  Setting explict TTLs on the other
> > 	records will allow all servers to return the TTL you want for the
> > 	forward records.
> > 
> > 	Mark
> 
> Good point, but I couldn't set explicit TTLs because the RRs were
> generated dynamically by DHCP.

	The DHCP server will be setting explict TTLs in the update
	requests.

> In short, what I needed was an
> alternate way to set the TTL without using the MINIMUM field. Finally,
> I've found out that my non RFC 2308 server has a "defTTL" parameter
> that can be set on a zone per zone basis, and that overrides the
> MINIMUM field of the SOA. With that, I can follow your suggestion, and
> get "sort of" RFC 2308-compatibility.
> 
> Thanks everybody for your help.
> 
>                              Joan
> 
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at isc.org