Here's where I show my ignorance....

What's the downside of going to bind 9?

I could also install the latest bind 8 (8.4.1) from ISC.  Does that not
fix it?

What would the best way to do this without making extra work for myself
on the next upgrade?

I'm going to run a web server on this box, so this is kind of a big deal
for me.

Thanks,

-dgl-

At 6:18 AM -0600 7/28/03, Alastair Rankine wrote:
>Hi,
>
>I've had this problem with BIND 8 since I started using NetBSD/macppc (around 1.5).
>
>Best solution I've found is to upgrade to bind 9. :/
>
>
>At 10:52 PM 7/27/2003 -0500, 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))