Caching DNS server error (lame server resolving)

Iggyboo · 02-23-2005, 10:06 PM

Slackware 10.1

I have been trying to get this DNS server up and running for a few days now, but I keep getting these "lame server resolving" errors. I have tried to use the prepackaged caching-nameserver-example that comes with Slackware, but it didn't work. I have tried the TLDP's DNS Howto for the Caching DNS setup, but, again, no luck. I have been examining my log an have noticed this error whenever I try to do a lookup:

Code:

Feb 23 21:25:48 router named[4045]: lame server resolving 'google.com' (in 'google.com'?): 216.239.32.10#53

or :

Code:

Feb 23 21:27:21 router named[4045]: lame server resolving 'yahoo.com' (in 'yahoo.com'?): 66.163.169.170#53
Feb 23 21:27:22 router named[4045]: lame server resolving 'yahoo.com' (in 'yahoo.com'?): 63.250.206.138#53
Feb 23 21:27:22 router named[4045]: lame server resolving 'yahoo.com' (in 'yahoo.com'?): 216.109.116.17#53
Feb 23 21:27:22 router named[4045]: lame server resolving 'yahoo.com' (in 'yahoo.com'?): 217.12.4.104#53
Feb 23 21:27:22 router named[4045]: lame server resolving 'yahoo.com' (in 'yahoo.com'?): 66.218.71.63#53

I should have all the root nameservers correct because I have built a root.hints file with a dig already, but that didn't fix it either.

The irony is that I had no problem when set up my friend's server...

The only difference between us? ISPs.

I have SpeedNet Wireless and he has RoadRunner Cable. I pay for a routable ip address form my ISP and can easily nmap to myself from my friends system. Port 53 shows to be open and accepting data. Would it be possible that my ISP is blocking my internal DNS server from performing its own lookups?

This is driving me CRAZY!

Help....me...,...please....!

linuxxed · 02-24-2005, 03:43 AM

Is that entry in the log worrying you or can you not get BIND to work at all?

From the manual:

"""A DNS server which is supposed to be authoritative for a zone, but isnt.

If you see something like this:

Aug 7 00:57:37 colo named[827]: lame server resolving '98.96-27.40.119.62.in-addr.arpa' (in '96-27.40.119.62.in-addr.arpa'?): 62.119.40.115#53

in your BIND logs, then BIND has queried a lame server. In this case, 62.119.40.115 is mentioned as being authoritative somewhere for the zone 98.96-27.40.119.62.in-addr.arpa, but when BIND queries it, it discovers that 62.119.40.115 is not authoritative, and logs that message. The SysAdmin at the other end needs to get a clue and fix his DNS. """"""""

If you've configured your DNS correctly and opened (UDP and TCP) on 53. And added this line

query-source address * port 53; to named.conf

Get on a network outside your LAN and do a simple telnet to 53 port to your name server. If you can connect then fine. Try

nslookup
>set server [yournameserverip]
>set type=A
>yahoo.com

See if this resolves correctly. If not then your nameserver has not been configured correctly.