Matthias Scheler wrote:
> Recently I reconfigured the "named" on one of my NetBSD-i386 1.2 systems to
> forward requests to a NetBSD-i386 1.1 system running the 1.2 BIND software
> (statically linked). From that moment on I got problems resolving CNAME
> records from a domain my named is primary for. "named" log error messages
> like this:
> 
> Nov 14 13:10:37 colwyn named[118]: Lame server on 'Susi.Informatik.RWTH-Aachen.DE' (in 'informatik.rwth-aachen.de'?): [194.121.202.132].53 
> 
> [194.121.202.132 is the 1.1 system to which requests are forwarded.]

...

> Compiling and installing BIND 4.9.5 fixes this problem. So there are two
> possible reasons for this bug:
> 
> 1.) It's a bug in BIND 4.9.3-P1
> 2.) NetBSD's name server and resolver library don't match.

These messages appear because the code in BIND 4.9.3 (by default) generates
error messages when it detects a DNS problem.  There was a discussion on the
newsgroup (comp.protocols.tcp-ip.domains) about this 12 months ago or so.
In later versions, the option is off by default - which is why you don't see
the problem in 4.9.5.  This isn't a bug in NetBSD.

You might like to check your DNS setup.  See the doc/misc/FAQ* files (in
4.9.5 at least) in the bind distribution for more information and check the
defines for LAME_* in conf/options.h.

J

-- 
"Railways have always been plagued by politicians, and it is not hard to
think that Robert Stephenson had the right idea when he drove his engine
over one of them at the opening of the Liverpool & Manchester Railway"

-- 
"Railways have always been plagued by politicians, and it is not hard to
think that Robert Stephenson had the right idea when he drove his engine
over one of them at the opening of the Liverpool & Manchester Railway"