lame server resolving error is not being negative cache in BIND9?

[Mark_Andrews at isc.org]

> Hi,
> 
> I found that my BIND 9 sever responds slower than BIND 8 server when it
> comes to resolving requests that are classified under lame server resolving
> error:
> 
> Sep 11 18:09:51.597 lame-servers: info: lame server resolving
> '0.0.217.65.in-addr.arpa' (in '0.217.65.in-addr.arpa'?): 208.233.96.254#53
> 
> I suspect this error is not being negative cached by BIND 9 any more.
> 
> In short 10 times of "nslookup 0.0.217.65.in-addr.arpa. <BIND8 server>" is
> faster than 10 times of "nslookup 0.0.217.65.in-addr.arpa. <BIND9 server>".
> 
> Is it the normal behaviour of BIND 9? Is there any option to speed up the
> server to reply such error?

	BIND 9 caches lame servers.  It avoids using lame servers but will
	use them it if exhausts all other servers for the zone.

	In this case there is only one server (ns1.airface.com) and it is
	lame so it will be tried.

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