lame servers resolving

[slim]

On Thu, 2004-06-24 at 10:20, Alexander Dalloz wrote:
> Am Do, den 24.06.2004 schrieb olga at urbantimes.net um 16:56:
> 
> > Since I am on the topic of logs... Here's another question.
> > I am getting a lot of 'lame server resolving' messages in the
> > /var/log/messages.
> > 
> > Here's an example:
> > Jun 24 09:02:25 isis named[1340]: lame server resolving
> > '71.68.90.80.in-addr.arpa' (in '68.90.80.in-addr.arpa'?): 80.90.64.38#53
> > 
> > Is this normal or does it mean that something is misconfigured or missing
> > in the bind configuration.
> > 
> > Olga
> 
> You can safely ignore such lame server messages, or even suppress them
> with following entry in the logging section of named.conf:
> 
>         category lame-servers {
>                 null;
>         };
> 
> A "lame server" is one that should be authoritative for a zone,
> according to the NS records that delegate authority for that zone, but
> really isn't, perhaps because it hasn't been configured to load the zone
> or because it is a secondary master that has expired the zone.
> 
> Alexander
> 

Mine is at the end just above include "/etc/rndc.key";