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

Re: lame servers resolving



Never mind, I found out the answer (it goes in the logging section).

> Where exactly should this entry belong in named.conf? I tried putting it
> in the options section or after it and in both cases it gave me an error.
>
>>
>> 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
>> --
>> fedora-list mailing list
>> fedora-list redhat com
>> To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
>>
>
>
> --
> fedora-list mailing list
> fedora-list redhat com
> To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
>



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