Eric Shubert wrote:
There are also some lame-server messages from bind that can be annoying,
as they get picked up by logwatch. To get rid of them, modify your
named.caching-nameserver.conf file as such in the logging section:
logging {
channel default_debug {
file "data/named.run";
severity dynamic;
};
category lame-servers { null; };
};
I just discovered that editing the named.caching-nameserver.conf file
isn't a good idea, as any changes will be lost if/when the
caching-nameserver package is updated. Instead, create any customization
in a separate named.conf file:
# echo "// customizations for named" \
> >/var/named/chroot/etc/named.conf
# echo "logging {" \
> >>/var/named/chroot/etc/named.conf
# echo " category lame-servers { null; };" \
> >>/var/named/chroot/etc/named.conf
# echo "};" \
> >>/var/named/chroot/etc/named.conf
# ln -s /var/named/chroot/etc/named.conf /etc/named.conf
--
-Eric 'shubes'
---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
