am3n portfolio

Tired seeing lame server error on your BIND (DNS server) log?

Dec 14 17:26:29 ns named[14961]: lame server resolving
'163.98.42.89.in-addr.arpa'(in '98.42.89.in-addr.arpa'?):
85.120.66.98#53
Dec 14 17:26:36 ns named[14961]: lame server resolving
'163.98.42.89.in-addr.arpa'(in '98.42.89.in-addr.arpa'?):
85.120.66.100#53
Dec 14 17:26:36 ns named[14961]: lame server resolving
'163.98.42.89.in-addr.arpa'(in '98.42.89.in-addr.arpa'?):
85.120.66.100#53

Those lines can make your /var/log/message file big pretty easily and consume your harddisk space.  So edit your named.conf (/etc/named.conf or /var/named/chroot/etc/named.conf) and create a new logging section and add below lines:

# vi /etc/named.conf

logging {   category "lame-servers" {
     "null";
   };
};

# service named restart

You can put it between options and zone sections.

Info from: Web Hosting Talk and Linux Questions

Related posts:

1. Install SSH (SFTP) server on Windows 2000 Below is step-by-step installation SSH (and SFTP) server on Windows...

Related posts brought to you by Yet Another Related Posts Plugin.

This entry was posted on Monday, December 14th, 2009 at 5:37 pm and is filed under Others, Web and System Administrator. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.