Getting Rid of BIND’s “lame server” Messages
Tweet
Related Posts:Upgrading ProCurve firmware via TFTP IIS 6.0 may not function correctly after installing KB973917 Busting an idiot reading a friend’s mail VMware Converter is Stupid T-Mobile’s BlackBerry support lacking
if, like me, you run bind, then you’ve probably encountered the “lame server” error messages in your logs at some point.
to be honest, they’re really not errors. they’re more warnings than anything, because the problem is actually with the remote server and not yours.
nevertheless, they can really build up over time and i, personally, don’t really care to see ‘em. to keep them out of your logs altogether, put the following near the top of your named.conf, then reload/restart bind:
logging { category lame-servers { null; }; };
Related Posts:



Recent Comments