ServerTune Logo Dedicated Servers Colocation VPS Server Management ServerTune.com
 
ServerTune HomeAbout usContact usHelp DeskKnowledgebaseSpecialLIVE Chat ServerTune
DirectAdmin VPS Server Management

Value, Power, and Performance :: Dedicated Servers starting $89 /month

Dedicated Server Hosting

Click here to view photos from the conferences we attended.   *** Follow ServerTune on: ServerTune is on Facebook ServerTune is on Twitter
 
Browse by category   Search
 


Error: lame server resolving
Printer Friendly
email to a friend
Email to friend
Add comment Add comment
Views: 2533
Votes: 0
Comments: 0
Posted: 24 Dec, 2007
by: Customer Service :: S.
* * * * *
Updated: 24 Dec, 2007
by: Customer Service :: S.

I see this error message in my log file:

    Dec 12 11:30:21 server1 named[xxxxx]: lame server resolving '62.114.34.74.in-addr.arpa' (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; };
Other articles in this Category
document What is round robin DNS?



RSS

Control Panel Licensing
cPanel Plesk Miva Merchant