Follow up on "query section mismatch" problem with NetBSD 1.6.1 on
my beige G3....

In response to my pleas for help, I only got one response, and that
was that I should upgrade to BIND 9.

Being a coward, I chose a slightly less adventurous path.
 
I downloaded BIND 8.4.1 source from ISC, and followed the directions
for build and install.  I held my nose, used the default install
variables, and did the "blind" "make install" as root.

ndc stop... ndc start....

....no more "query section mismatch" log messages.  It seems to be working.

I _am_ getting some IPv6 whines from bind, but those are probably
"normal" given that I have no IPv6 connectivity.

Does anyone know of any nasty surprises along my chosen path?

Does anyone know if this problem will be addressed in NetBSD 1.6.2?

Thanks,

-dgl-

At 10:52 PM -0500 7/27/03, Donald Lee wrote:
>Does anyone recognize the following messages from bind? (see below)
>
>NetBSD 1.6.1 runs bind 8.3.4, which according to what I can find on the net
>should have this particular bug fixed.
>
>Is this a known problem?  Am I doing something silly?
>
>I get *lots* of these messages, and it appears that they 
>are mostly (all?) bogus.
>
>Thanks,
>
>-dgl-
>
>
>Jul 27 22:27:51 grace named[102]: Malformed response from [209.46.8.66].53 (query section mismatch (time.icompute.com IN A))
>Jul 27 22:28:14 grace named[102]: Malformed response from [198.4.83.35].53 (query section mismatch (ns.watson.ibm.com IN AAAA))
>Jul 27 22:28:14 grace named[102]: Malformed response from [195.176.20.204].53 (query section mismatch (internet-server.zurich.ibm.com IN A6))
>Jul 27 22:28:22 grace named[102]: Malformed response from [192.35.232.34].53 (query section mismatch (ns.watson.ibm.com IN A6))
>Jul 27 22:28:22 grace named[102]: Malformed response from [129.34.20.80].53 (query section mismatch (ns.almaden.ibm.com IN AAAA))