lame server showing up in logs constantly and name server eventually hangs

Ali Eghtessadi ali at babcockbrown.com
Wed Feb 19 17:22:27 UTC 2003 

Dear All,

I am seeing the following messages in my log file.  When I do a " tail 
-f named.log", messages are being displayed as fast as my computer can 
display them. I have looked at the bind new group and read about the 
issue with lame name servers and what causes this to happen. But this is 
a bit unusual to see so many messages.  One other things that happens is 
that after a while, my name server stops resolving any addresses and the 
only way to fix it is to reboot the server.  I am running bind 9.2.1 on 
solaris 9.

Here are some sample messages :

Feb 19 09:16:55 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '2.38.214.202.in-addr.arpa' (in 
'38.214.202.in-addr.arpa'?): 202.232.2.35#53
Feb 19 09:16:55 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '127.94.151.209.in-addr.arpa' (in 
'94.151.209.in-addr.arpa'?): 209.197.254.36#53
Feb 19 09:16:55 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '126.94.151.209.in-addr.arpa' (in 
'94.151.209.in-addr.arpa'?): 209.197.254.36#53
Feb 19 09:16:55 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '127.94.151.209.in-addr.arpa' (in 
'94.151.209.in-addr.arpa'?): 209.197.254.36#53
Feb 19 09:16:55 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '126.94.151.209.in-addr.arpa' (in 
'94.151.209.in-addr.arpa'?): 209.197.254.36#53
Feb 19 09:16:56 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '62.135.86.202.in-addr.arpa' (in 
'135.86.202.in-addr.arpa'?): 209.68.2.89#53
Feb 19 09:16:56 alcatraz.babcockbrown.com last message repeated 1 time
Feb 19 09:16:57 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '4.236.100.206.in-addr.arpa' (in 
'236.100.206.in-addr.arpa'?): 208.34.224.11#53
Feb 19 09:16:57 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '150.133.25.218.in-addr.arpa' (in 
'25.218.in-addr.arpa'?): 202.96.64.68#53
Feb 19 09:16:57 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '10.11.224.199.in-addr.arpa' (in 
'10.11.224.199.in-addr.arpa'?): 198.144.230.11#53
Feb 19 09:16:58 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '150.133.25.218.in-addr.arpa' (in 
'25.218.in-addr.arpa'?): 202.96.75.68#53
Feb 19 09:16:58 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '4.236.100.206.in-addr.arpa' (in 
'236.100.206.in-addr.arpa'?): 208.34.224.11#53
Feb 19 09:16:59 alcatraz.babcockbrown.com last message repeated 2 times
Feb 19 09:16:59 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '150.133.25.218.in-addr.arpa' (in 
'25.218.in-addr.arpa'?): 202.96.64.68#53
Feb 19 09:17:00 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '2.51.63.211.in-addr.arpa' (in 
'51.63.211.in-addr.arpa'?): 211.234.98.11#53
Feb 19 09:17:00 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '62.135.86.202.in-addr.arpa' (in 
'135.86.202.in-addr.arpa'?): 209.68.2.89#53
Feb 19 09:17:00 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '2.51.63.211.in-addr.arpa' (in 
'51.63.211.in-addr.arpa'?): 211.234.98.12#53
Feb 19 09:17:00 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '62.135.86.202.in-addr.arpa' (in 
'135.86.202.in-addr.arpa'?): 209.68.2.89#53
Feb 19 09:17:01 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving 'NS.IOS.DOI.GOV' (in 'IOS.DOI.GOV'?): 
198.246.66.197#53
Feb 19 09:17:01 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '155.50.75.200.in-addr.arpa' (in 
'50.75.200.in-addr.arpa'?): 63.171.232.38#53
Feb 19 09:17:01 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '150.133.25.218.in-addr.arpa' (in 
'25.218.in-addr.arpa'?): 202.96.75.68#53
Feb 19 09:17:01 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '155.50.75.200.in-addr.arpa' (in 
'50.75.200.in-addr.arpa'?): 63.171.232.39#53
Feb 19 09:17:01 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '155.50.75.200.in-addr.arpa' (in 
'50.75.200.in-addr.arpa'?): 63.171.232.38#53
Feb 19 09:17:01 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '155.50.75.200.in-addr.arpa' (in 
'50.75.200.in-addr.arpa'?): 63.171.232.39#53
Feb 19 09:17:01 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '150.133.25.218.in-addr.arpa' (in 
'25.218.in-addr.arpa'?): 202.96.75.68#53
Feb 19 09:17:02 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '3.102.102.202.in-addr.arpa' (in 
'102.102.202.in-addr.arpa'?): 202.102.29.3#53
Feb 19 09:17:02 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '4.221.196.210.in-addr.arpa' (in 
'221.196.210.in-addr.arpa'?): 210.141.108.248#53
Feb 19 09:17:02 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '155.50.75.200.in-addr.arpa' (in 
'50.75.200.in-addr.arpa'?): 63.171.232.38#53
Feb 19 09:17:02 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '155.50.75.200.in-addr.arpa' (in 
'50.75.200.in-addr.arpa'?): 63.171.232.39#53
Feb 19 09:17:03 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '150.133.25.218.in-addr.arpa' (in 
'25.218.in-addr.arpa'?): 202.96.64.68#53
Feb 19 09:17:03 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '155.50.75.200.in-addr.arpa' (in 
'50.75.200.in-addr.arpa'?): 63.171.232.38#53
Feb 19 09:17:03 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '155.50.75.200.in-addr.arpa' (in 
'50.75.200.in-addr.arpa'?): 63.171.232.39#53
Feb 19 09:17:03 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving 'ns.spt.net.cn' (in 'spt.net.CN'?): 
202.96.0.133#53
Feb 19 09:17:03 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving 'ns.spt.net.cn' (in 'spt.net.CN'?): 
202.96.199.133#53
Feb 19 09:17:03 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving 'ns.gdgzptt.net.cn' (in 
'gdgzptt.net.CN'?): 202.103.224.68#53
Feb 19 09:17:04 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '150.133.25.218.in-addr.arpa' (in 
'25.218.in-addr.arpa'?): 202.96.75.68#53
Feb 19 09:17:05 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '140.220.86.213.in-addr.arpa' (in 
'86.213.in-addr.arpa'?): 195.110.64.11#53
Feb 19 09:17:05 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving '150.133.25.218.in-addr.arpa' (in 
'25.218.in-addr.arpa'?): 202.96.64.68#53
Feb 19 09:17:05 alcatraz.babcockbrown.com named[128]: [ID 866145 
daemon.info] lame server resolving 'ns.spt.net.cn' (in 'spt.net.CN'?): 
202.96.128.68#53
#

I appreciate any help I can get with this issue.  Here is a copy of my 
/etc/named.conf
# more /etc/named.conf
options {
        directory "/var/named";
        query-source address * port 53;
        allow-transfer { none; };
};

logging {
        channel chatty { syslog daemon; severity debug; };
        category config { chatty; };
        category default { chatty; };
        category general { chatty; };
};

# controls for rndc
controls {
        inet 127.0.0.1 allow { 127.0.0.1; } keys { "rndckey"; };
};

acl sprint-servers { 144.228.254.10; 206.228.179.10; 144.228.255.10; };

acl babcockbrown-servers { a.b.c.d; a.b.c.e; };
#
# Secure key defenitions file
#
include "/etc/rndc.key";

#
#       Zone Files
#
include "/var/named/named.conf.active-zones";
#
include "/var/named/named.conf.reserved-zones";
#
#       PTR records for a.b.c
#
zone "a.b.c.in-addr.arpa" in {
        type master;
        file "master-active/a.b.c";
        allow-query { any; };
};


#       Local Loopback
zone "0.0.127.in-addr.arpa" in {
        type master;
        file "master-active/127.0.0";
        allow-query { any; };
};

zone "." in {
        type hint;
        file "named.ca";
};
#

More information about the bind-users mailing list