Tuesday, September 29, 2009

Bind Error: lame server resolving

SkyHi @ Tuesday, September 29, 2009
I see this error message in my log file:

Dec 12 11:30:21 server1 named[xxxxx]: lame server resolving '' (in '114.34.74.in-addr.arpa'?)

What does that mean and how can I get rid of it?

Lame server is one that is advertised to have authoritative information about a domain, but doesn't. This can happen in a few different ways, but it's usually not worth the trouble to track down the administrator of the other domain. TO solve this issue, add this directive to /etc/named.conf in the "options" section:

version "not currently available";
allow-recursion { trusted; };
allow-notify { trusted; };
allow-transfer { trusted; };

This will allow you to run your own zones as a master, and stop anyone but your server from using your DNS to look up hosts you aren't authoratative for (recursive lookups). That should eliminate the possibility that someone else's queries causing this issue.

If you wish to clean up the logs, add this to /etc/named.conf, below the options section:

logging {
category lame-servers { null; };

Reference: http://servertune.com/kbase/entry/227/