>Number:         2943
>Category:       bin
>Synopsis:       named doesn't work if forwarder is used
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people (Utility Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Nov 15 12:35:01 1996
>Last-Modified:
>Originator:     Matthias Scheler
>Organization:
Matthias Scheler
tron@lyssa.owl.de
>Release:        961027
>Environment:
	
System: NetBSD lyssa 1.2B NetBSD 1.2B (LYSSA) #0: Fri Nov 8 23:32:14 MET 1996 tron@lyssa:/usr/src/sys/arch/i386/compile/LYSSA i386


>Description:
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.]

>How-To-Repeat:
Setup two name serves as described and try to resolv CNAME records from a
domain for which the slave "named" is a primary.

>Fix:

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.

Any way I suggest to integrate BIND 4.9.5 into the source tree. I'm willing
to do this if someone with CVS access offers me some support because I don't
want to send this whole beast as a PR.
>Audit-Trail:
>Unformatted: