[TriLUG] caching nameserver question

[Aaron S. Joyner]

William Sutton wrote:

>I have a Sony Vaio running Red Hat 9 and the freshrpms yum and 
>caching-nameserver.  At the moment /var/log/messages is taking up 21 megs 
>of disk space, and appears to consist entirely of caching-nameserver 
>messages:
>
>Oct 17 04:57:49 corran named[2116]: lame server resolving 'localhost.<fake domain>.com' (in 'hippogeek.com'?): 63.209.15.211#53
>
>where <fake domain> has been substituted for the purpose of this email in 
>place of a DynDNS domain that I still haven't gotten working :)
>  
>
You neglect to mention what your named.conf looks like, or what the zone 
file for <fake domain>.com looks like.  That's where the problem really 
lies.

>So the question is, where is my log message coming from and how can I put 
>a stop to it?  This puppy doesn't have a lot of disk space and I'm getting 
>tired of manually zeroing out the logs to keep the disk from filling up :)
>
The log message is being generated because your server is a lame server 
for that domain, most likely.  In other words, you have a configuration 
which advertises that you are authoritative for that domain, but you're 
really not authoritative.  There are two ways to suppress the errors.  
The "right" way, is to fix the configuration for that domain.  But it 
seems as if you're more interested in just suppressing the error, and as 
you haven't provided sufficient information about your BIND setup I 
can't really help with that part.  To suppress the error, you can put an 
entry in the logging {} section of your named.conf which says:
logging {
     category lame-servers { null; };
};

What this basically says, is for the logging category lame-servers, 
don't put them into a file, but log them to null instead (effectively 
throwing them away).  If you don't have a logging section, then you can 
add one, I'd suggest putting it right after the options {} section, 
towards the top, but the location is really irrelevant (as long as it's 
not inside of another section).

For more complete details, check the Bind9 Administrator's Reference 
Manual, specifically this section:
http://www.bind9.net/Bv9ARM.ch06.html#AEN1607

If you want to clean up that name server so it doesn't generate those 
messages to start with, post the configs and I'll see what I can 
recommend, or head over to the DNS class this coming November and we'll 
get you all straightened out.  :)

Aaron S. Joyner