Todd Lyons grabbed a keyboard and wrote:
>
> David Guntner wrote on Thu, Dec 05, 2002 at 02:47:21PM -0800 :
> >
> > Of late, I've been getting TONS of "named: lame server resolving ...."
> > messages anytime a DNS lookup takes place locally. I've got the caching
> > nameserver package installed, with BIND9. ML 9.0. Anyone have any ideas
> > what would be causing this? My syslog is starting to get really
> > crowded.... :-)
>
> Post the messages.
Ok, here's a sample:
Dec 5 16:19:43 janet named[1144]: lame server resolving '53.43.67.66.opm.blitzed.org'
(in 'blitzed.org'?): 66.45.120.62#53
Dec 5 16:19:43 janet named[1144]: lame server resolving '53.43.67.66.opm.blitzed.org'
(in 'blitzed.org'?): 207.8.219.201#53
Dec 5 16:19:43 janet named[1144]: lame server resolving '53.43.67.66.opm.blitzed.org'
(in 'blitzed.org'?): 194.196.163.7#53
Dec 5 16:19:43 janet named[1144]: lame server resolving '53.43.67.66.opm.blitzed.org'
(in 'blitzed.org'?): 205.158.174.201#53
Dec 5 16:19:43 janet named[1144]: lame server resolving '53.43.67.66.opm.blitzed.org'
(in 'blitzed.org'?): 140.186.128.222#53
Dec 5 16:19:43 janet named[1144]: lame server resolving '53.43.67.66.opm.blitzed.org'
(in 'blitzed.org'?): 192.148.252.53#53
Dec 5 16:19:44 janet named[1144]: lame server resolving
'53.43.67.66.opm.blitzed.org.rhpsfan.org' (in 'rhpsfan.org'?): 166.90.15.234#53
Dec 5 16:19:44 janet named[1144]: lame server resolving
'53.43.67.66.opm.blitzed.org.rhpsfan.org' (in 'rhpsfan.org'?): 166.90.15.235#53
Dec 5 16:19:44 janet named[1144]: lame server resolving
'53.43.67.66.opm.blitzed.org.rhpsfan.org' (in 'rhpsfan.org'?): 64.39.31.103#53
Dec 5 16:19:44 janet named[1144]: lame server resolving
'53.43.67.66.korea.services.net.rhpsfan.org' (in 'rhpsfan.org'?): 166.90.15.234#53
Dec 5 16:19:44 janet named[1144]: lame server resolving
'53.43.67.66.korea.services.net.rhpsfan.org' (in 'rhpsfan.org'?): 166.90.15.235#53
Dec 5 16:19:44 janet named[1144]: lame server resolving
'53.43.67.66.korea.services.net.rhpsfan.org' (in 'rhpsfan.org'?): 64.39.31.103#53
Dec 5 16:19:44 janet named[1144]: lame server resolving '53.43.67.66.dnsbl.njabl.org'
(in 'dnsbl.njabl.org'?): 209.208.0.97#53
Dec 5 16:19:45 janet named[1144]: lame server resolving '53.43.67.66.dnsbl.njabl.org'
(in 'dnsbl.njabl.org'?): 209.208.0.96#53
Dec 5 16:19:45 janet named[1144]: lame server resolving
'53.43.67.66.dnsbl.njabl.org.rhpsfan.org' (in 'rhpsfan.org'?): 166.90.15.235#53
Dec 5 16:19:45 janet named[1144]: lame server resolving
'53.43.67.66.dnsbl.njabl.org.rhpsfan.org' (in 'rhpsfan.org'?): 166.90.15.234#53
Dec 5 16:19:45 janet named[1144]: lame server resolving
'53.43.67.66.dnsbl.njabl.org.rhpsfan.org' (in 'rhpsfan.org'?): 64.39.31.103#53
Dec 5 16:19:46 janet named[1144]: lame server resolving '55.68.74.204.bl.spamcop.net'
(in 'bl.spamcop.NET'?): 64.113.39.10#53
Dec 5 16:19:46 janet named[1144]: lame server resolving '55.68.74.204.bl.spamcop.net'
(in 'bl.spamcop.NET'?): 194.109.6.147#53
Dec 5 16:19:46 janet named[1144]: lame server resolving '55.68.74.204.bl.spamcop.net'
(in 'bl.spamcop.NET'?): 65.242.88.99#53
Dec 5 16:19:46 janet named[1144]: lame server resolving '55.68.74.204.bl.spamcop.net'
(in 'bl.spamcop.NET'?): 205.231.29.242#53
Dec 5 16:19:47 janet named[1144]: lame server resolving
'55.68.74.204.mail.services.net' (in 'mail.services.NET'?): 208.31.42.99#53
Dec 5 16:19:49 janet named[1144]: lame server resolving
'241.28.13.206.relays.ordb.org' (in 'relays.ordb.org'?): 194.239.134.82#53
Dec 5 16:19:49 janet named[1144]: lame server resolving
'241.28.13.206.relays.ordb.org' (in 'relays.ordb.org'?): 194.255.24.145#53
Dec 5 16:19:49 janet named[1144]: lame server resolving
'241.28.13.206.relays.ordb.org' (in 'relays.ordb.org'?): 130.226.1.4#53
Dec 5 16:19:49 janet named[1144]: lame server resolving
'241.28.13.206.relays.ordb.org' (in 'relays.ordb.org'?): 193.162.159.97#53
Dec 5 16:19:49 janet named[1144]: lame server resolving
'241.28.13.206.relays.ordb.org' (in 'relays.ordb.org'?): 216.240.41.21#53
Dec 5 16:19:49 janet named[1144]: lame server resolving
'241.28.13.206.relays.ordb.org' (in 'relays.ordb.org'?): 195.86.49.227#53
Dec 5 16:19:49 janet named[1144]: lame server resolving
'241.28.13.206.relays.ordb.org' (in 'relays.ordb.org'?): 212.242.41.170#53
Dec 5 16:19:49 janet named[1144]: lame server resolving
'241.28.13.206.relays.ordb.org' (in 'relays.ordb.org'?): 62.242.234.100#53
Dec 5 16:19:50 janet named[1144]: lame server resolving
'241.28.13.206.relays.ordb.org.rhpsfan.org' (in 'rhpsfan.org'?): 166.90.15.235#53
Dec 5 16:19:50 janet named[1144]: lame server resolving
'241.28.13.206.relays.ordb.org.rhpsfan.org' (in 'rhpsfan.org'?): 166.90.15.234#53
Dec 5 16:19:50 janet named[1144]: lame server resolving
'241.28.13.206.relays.ordb.org.rhpsfan.org' (in 'rhpsfan.org'?): 64.39.31.103#53
Dec 5 16:19:50 janet named[1144]: lame server resolving
'241.28.13.206.relays.visi.com' (in 'relays.visi.com'?): 209.98.98.115#53
Dec 5 16:19:50 janet named[1144]: lame server resolving
'241.28.13.206.relays.visi.com.rhpsfan.org' (in 'rhpsfan.org'?): 166.90.15.234#53
Dec 5 16:19:50 janet named[1144]: lame server resolving
'241.28.13.206.relays.visi.com.rhpsfan.org' (in 'rhpsfan.org'?): 64.39.31.103#53
Dec 5 16:19:50 janet named[1144]: lame server resolving
'241.28.13.206.relays.visi.com.rhpsfan.org' (in 'rhpsfan.org'?): 166.90.15.235#53
Dec 5 16:19:50 janet named[1144]: lame server resolving
'241.28.13.206.bl.spamcop.net' (in 'bl.spamcop.NET'?): 64.113.39.10#53
Dec 5 16:19:50 janet named[1144]: lame server resolving
'241.28.13.206.bl.spamcop.net' (in 'bl.spamcop.NET'?): 194.109.6.147#53
Dec 5 16:19:50 janet named[1144]: lame server resolving
'241.28.13.206.bl.spamcop.net' (in 'bl.spamcop.NET'?): 65.242.88.99#53
Dec 5 16:19:50 janet named[1144]: lame server resolving
'241.28.13.206.bl.spamcop.net' (in 'bl.spamcop.NET'?): 205.231.29.242#53
Dec 5 16:19:51 janet named[1144]: lame server resolving
'241.28.13.206.bl.spamcop.net.rhpsfan.org' (in 'rhpsfan.org'?): 64.39.31.103#53
Dec 5 16:19:51 janet named[1144]: lame server resolving
'241.28.13.206.bl.spamcop.net.rhpsfan.org' (in 'rhpsfan.org'?): 166.90.15.234#53
Dec 5 16:19:51 janet named[1144]: lame server resolving
'241.28.13.206.bl.spamcop.net.rhpsfan.org' (in 'rhpsfan.org'?): 166.90.15.235#53
Dec 5 16:19:51 janet named[1144]: lame server resolving
'241.28.13.206.sbl.spamhaus.org' (in 'sbl.spamhaus.org'?): 205.158.174.201#53
Dec 5 16:19:51 janet named[1144]: lame server resolving
'241.28.13.206.sbl.spamhaus.org' (in 'sbl.spamhaus.org'?): 194.196.163.7#53
Dec 5 16:19:51 janet named[1144]: lame server resolving
'241.28.13.206.sbl.spamhaus.org' (in 'sbl.spamhaus.org'?): 140.186.128.222#53
Dec 5 16:19:51 janet named[1144]: lame server resolving
'241.28.13.206.sbl.spamhaus.org' (in 'sbl.spamhaus.org'?): 66.45.120.62#53
Dec 5 16:19:51 janet named[1144]: lame server resolving
'241.28.13.206.sbl.spamhaus.org' (in 'sbl.spamhaus.org'?): 207.8.219.201#53
Dec 5 16:19:51 janet named[1144]: lame server resolving
'241.28.13.206.sbl.spamhaus.org' (in 'sbl.spamhaus.org'?): 192.148.252.53#53
Dec 5 16:19:51 janet named[1144]: lame server resolving
'241.28.13.206.sbl.spamhaus.org' (in 'sbl.spamhaus.org'?): 196.36.190.96#53
Dec 5 16:19:51 janet named[1144]: lame server resolving
'241.28.13.206.sbl.spamhaus.org' (in 'sbl.spamhaus.org'?): 147.123.151.252#53
Dec 5 16:19:51 janet named[1144]: lame server resolving
'241.28.13.206.sbl.spamhaus.org' (in 'sbl.spamhaus.org'?): 147.102.222.210#53
Dec 5 16:19:51 janet named[1144]: lame server resolving
'241.28.13.206.sbl.spamhaus.org' (in 'sbl.spamhaus.org'?): 193.190.198.2#53
Dec 5 16:19:51 janet named[1144]: lame server resolving
'241.28.13.206.sbl.spamhaus.org' (in 'sbl.spamhaus.org'?): 208.31.42.43#53
Dec 5 16:19:51 janet named[1144]: lame server resolving
'241.28.13.206.sbl.spamhaus.org' (in 'sbl.spamhaus.org'?): 217.160.72.252#53
Dec 5 16:19:51 janet named[1144]: lame server resolving
'241.28.13.206.sbl.spamhaus.org' (in 'sbl.spamhaus.org'?): 204.152.184.64#53
Dec 5 16:19:51 janet named[1144]: lame server resolving
'241.28.13.206.sbl.spamhaus.org' (in 'sbl.spamhaus.org'?): 194.109.6.146#53
Dec 5 16:19:51 janet named[1144]: lame server resolving
'241.28.13.206.sbl.spamhaus.org' (in 'sbl.spamhaus.org'?): 193.190.198.10#53
Dec 5 16:19:52 janet named[1144]: lame server resolving
'241.28.13.206.sbl.spamhaus.org.rhpsfan.org' (in 'rhpsfan.org'?): 64.39.31.103#53
Dec 5 16:19:52 janet named[1144]: lame server resolving
'241.28.13.206.sbl.spamhaus.org.rhpsfan.org' (in 'rhpsfan.org'?): 166.90.15.234#53
Dec 5 16:19:52 janet named[1144]: lame server resolving
'241.28.13.206.sbl.spamhaus.org.rhpsfan.org' (in 'rhpsfan.org'?): 166.90.15.235#53
Dec 5 16:19:52 janet named[1144]: lame server resolving
'241.28.13.206.mail.services.net' (in 'mail.services.NET'?): 208.31.42.99#53
As you can see, I get many entries for each one, and there are lots of 'em.
Once upon a time (fairly recently, even), I never used to see so many of
these.
> Normally this is when your name server tries to lookup some domain, but
> a name server that the root servers says is supposed to be
> authoritative says "I don't know, that's not my domain."
In that case, there seems to be a LOT of it going around.
[example deleted]
> So there are two name servers listed as authoritative for that domain.
> But if you query them, both respond with "." domain entries, which are
> the root dns entries. Since the servers which are listed as being
> authoritative are really not authoritative, they're called "lame
> servers."
So out of curiosity, how does the name eventually get resolved in these
cases? Obviously, someone is finally deciding to report an IP address, or
I wouldn't be doing a lot of web browsing and so on.... :-)
--Dave
--
David Guntner GEnie: Just say NO!
http://www.akaMail.com/pgpkey/davidg or key server
for PGP Public key
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
