DNS info disapears

[Mark_Andrews at isc.org]

> > 	The default changed when named was brought into compliance
> > 	with RFC 2038 (1999/01/02). 
> 
> It would be worthwhile to update `doc/html/options.html' in any future
> BIND 8 release to reflect this change that's been in effect since v8.2.

	Agreed.

> > 	This is max-ncache-ttl taking effect.
> > 
> > >   3.  The glue records (NS[12].shopcanberra.com) do not exist as
> > >       authoritative data.  Are the new rules in the credibility
> > >       pecking order such that an authoritative NXDOMAIN will
> > >       displace non-authoritative glue?
> > 
> > 	Of course.
> 
> This needs to be explored a bit further because this particular flavor
> of broken delegation for `shopcanberra.com' reveals two different kinds
> of BIND resolution behaviors - one for v8.3.2/8.3.3 exemplified by the
> above queries and another for previous versions of BIND 8 and the latest
> version of BIND 9 (9.2.2rc1).
 
	BIND 8 fetches missing glue (including AAAA) when returning
	answers (unless the answer is passed through).
	
	BIND 9 does not fetch missing glue when returning answers.

	The first answer was passed through.
	The second answer was from the cache causing lookups for
	AAAA ns[12].shopcanberra.com.
	The third lookup got the cached NXDOMAIN returned by the
	AAAA lookups.

	Garbage In - Garbage Out

	Mark
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at isc.org