Subject: Re: Troubleshooting lame server errors
From: Jason Jeremias (jasonj@uui-alaska.com)
Date: Thu Dec 05 2002 - 11:33:08 AKST
Try this, bind9 likes logging as its own category (not under options)
logging {
//
// Stop all the Lame Server messages
//
category lame-servers{ null; };
};
-Jason
Mike Tibor wrote:
>On Thu, 5 Dec 2002, Mike Barsalou wrote:
>
>
>
>>Can someone point me to some sort of guide about how to troubleshoot lame
>>server errors? My current understanding is that a lame server response is
>>just a DNS server that is supposed to be authoritative for a domain is not
>>really.
>>
>>Ideas?
>>
>>
>
>Yup, that's exactly it. About the only real thing you can do is tell
>named not to log such errors. I had the following in my bind8 named.conf:
>
>options {
> [...]
> logging {
> category lame-servers { null; };
> };
>};
>
>For some reason though bind9 didn't like it, and I haven't taken the time
>to figure out why yet.
>
>Mike
>
>
---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.
This archive was generated by hypermail 2a23 : Thu Dec 05 2002 - 14:47:19 AKST