Cache-Only Server Complains Abount Lame Server On Every Query

Auteria Wally Winzer Jr. wally.winzer at ChampUSA.COM
Mon Sep 6 01:46:18 UTC 1999


I've have 4 servers (1 primary, 2 secondary, and 1 cache-only).
For the authoritive servers I have the forwarders directive pointing
to the cache-only server:

forwarders { 204.118.92.7 };

So that the cache can be built up for faster responses over a period
of time.  When any primary/secondary server queries an outside address
the cache-only server complains that Lame server exists on every lookup
from 204.118.92.7:

Sep  5 03:50:31 whirlsvr named[8021]: Lame server on '72.2.123.204.in-addr.arpa'
(in '123.204.in-addr.arpa'?): [204.118.92.7].53
Sep  5 03:50:31 whirlsvr named[8021]: Lame server on '4.0.1.16.in-addr.arpa' (in
'16.in-addr.arpa'?): [204.118.92.7].53
Sep  5 03:50:36 whirlsvr named[8021]: Lame server on 'clepsydra.dec.com' (in
'DEC.com'?): [204.118.92.7].53
Sep  5 03:50:36 whirlsvr named[8021]: Lame server on
'72.184.152.204.in-addr.arpa' (in 'arpa'?): [204.118.92.7].53
Sep  5 03:50:36 bms12.WahLeeWHIRL.COM named[19806]: Lame server on
'4.0.1.16.in-addr.arpa' (in '16.in-addr.arpa'?): [204.118.92.7].53
Sep  5 03:50:36 whirlsvr named[8021]: Lame server on 'clock.isc.org' (in
'ORG'?): [204.118.92.7].53
Sep  5 03:57:09 whirlsvr named[8021]: Lame server on '4.0.1.16.in-addr.arpa' (in
'1.16.in-addr.arpa'?): [204.118.92.7].53
Sep  5 05:00:20 whirlsvr named[8021]: Lame server on '01-029.043.popsite.net'
(in 'NET'?): [204.118.92.7].53
Sep  5 09:42:21 whirlsvr named[8021]: Lame server on '92.35.51.198.in-addr.arpa'
(in 'arpa'?): [204.118.92.7].53
Sep  5 14:14:13 bms8.WahLeeWHIRL.COM named[3665]: Lame server on
'messenger.netscape.com' (in 'com'?): [204.118.92.7].53
Sep  5 14:14:15 bms8.WahLeeWHIRL.COM named[3665]: Lame server on
'home32.netscape.com' (in 'NETSCAPE.com'?): [204.118.92.7].53
Sep  5 14:21:11 bms8.WahLeeWHIRL.COM named[3665]: Lame server on
'imageserv2.imgis.com' (in 'IMGIS.com'?): [204.118.92.7].53
Sep  5 14:21:34 bms12.WahLeeWHIRL.COM named[19806]: Lame server on
'van.ads.link4ads.com' (in 'com'?): [204.118.92.7].53
Sep  5 14:21:39 whirlsvr named[8021]: Lame server on 'van.ads.link4ads.com' (in
'com'?): [204.118.92.7].53
Sep  5 17:30:35 bms8.WahLeeWHIRL.COM named[3665]: Lame server on
'72.184.152.204.in-addr.arpa' (in 'arpa'?): [204.118.92.7].53
Sep  5 17:30:40 bms12.WahLeeWHIRL.COM named[19806]: Lame server on
'72.184.152.204.in-addr.arpa' (in 'arpa'?): [204.118.92.7].53
Sep  5 17:30:45 whirlsvr named[8021]: Lame server on
'72.184.152.204.in-addr.arpa' (in 'arpa'?): [204.118.92.7].53
Sep  5 17:30:50 bms8.WahLeeWHIRL.COM named[3665]: Lame server on
'72.184.152.204.in-addr.arpa' (in '184.152.204.in-addr.arpa'?):
[204.118.92.7].53
Sep  5 17:31:37 whirlsvr named[8021]: Lame server on '72.2.123.204.in-addr.arpa'
(in '123.204.in-addr.arpa'?): [204.118.92.7].53
Sep  5 17:31:37 whirlsvr named[8021]: Lame server on 'usno.pa-x.dec.com' (in
'com'?): [204.118.92.7].53
Sep  5 17:31:38 whirlsvr named[8021]: Lame server on '4.0.1.16.in-addr.arpa' (in
'16.in-addr.arpa'?): [204.118.92.7].53
Sep  5 17:31:43 bms12.WahLeeWHIRL.COM named[19806]: Lame server on
'4.0.1.16.in-addr.arpa' (in '16.in-addr.arpa'?): [204.118.92.7].53
Sep  5 17:31:53 whirlsvr named[8021]: Lame server on '4.0.1.16.in-addr.arpa' (in
'1.16.in-addr.arpa'?): [204.118.92.7].53
Sep  5 17:31:53 whirlsvr named[8021]: Lame server on 'clepsydra.dec.com' (in
'DEC.com'?): [204.118.92.7].53
Sep  5 17:31:53 whirlsvr named[8021]: Lame server on
'72.184.152.204.in-addr.arpa' (in '184.152.204.in-addr.arpa'?):
[204.118.92.7].53
Sep  5 17:31:53 whirlsvr named[8021]: Lame server on 'clock.isc.org' (in
'ORG'?): [204.118.92.7].53

All secondary/cache-only servers has 3 nameserver directives within
its /etc/resolv.conf.  The 1st nameserver line has the IP address 0.0.0.0
(local machine).  The primary has its actual IP address as the first nameserver
directive within its config file.

Did I miss a configuration step somewhere?  I know clock.isc.org and
clepsydra.dec.com delegation is configured properly.

Thanks for any assistance in solving this issue.

- Wally Winzer Jr.



More information about the bind-users mailing list