[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: lame servers resolving



Am Do, den 24.06.2004 schrieb olga 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


-- 
Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13
Fedora GNU/Linux Core 2 (Tettnang) on Athlon CPU kernel 2.6.6-1.435 
Serendipity 17:14:06 up 1 day, 15:52, load average: 1.02, 1.27, 1.28 

Attachment: signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]