Bind 9 slave of Bind 8 hesiod zone

[Andris Kalnozols]

> > I believe your probelem is caused by incorrect handling of the HS
> > class by the BIND 8 master, as shown by the following dig output:
> > 
> >    $ dig ns.colorado.edu. hs soa @128.138.238.154
> >    ;; Warning: Message parser reports malformed message packet.
> > 
> >    ; <<>> DiG 9.2.0a2 <<>> ns.colorado.edu. hs soa @128.138.238.154
> >    ;; global options:  printcmd
> >    ;; Got answer:
> >    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24412
> >    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 4
> > 
> >    ;; QUESTION SECTION:
> >    ;ns.colorado.edu.               HS      SOA
> > 
> >    ;; ANSWER SECTION:
> >    ns.colorado.edu.        21600   HS      SOA     cujo.colorado.edu. postmast
> er.cu
> >    jo.colorado.edu. 200107120 3600 1200 2592000 21600
> > 
> >    ;; AUTHORITY SECTION:
> >    ns.colorado.edu.        21600   HS      NS      boulder.colorado.edu.
> >    ns.colorado.edu.        21600   HS      NS      cujo.colorado.edu.
> >    ns.colorado.edu.        21600   HS      NS      leather.colorado.edu.
> > 
> >    ;; ADDITIONAL SECTION:
> >    boulder.colorado.edu.   21600   IN      A       128.138.240.1
> >    boulder.colorado.edu.   21600   IN      A       128.138.238.18
> >    cujo.colorado.edu.      21600   IN      A       128.138.238.154
> >    leather.colorado.edu.   21600   IN      A       128.138.196.23
> > 
> > The master is sending class IN glue in a class HS response, and BIND 9
> > considers this to be sufficiently broken to reject the packet.
> > If this is the most recent version of BIND 8, you should report it
> > as a BIND 8 bug.
> > -- 
> > Andreas Gustafsson, gson at nominum.com
> --------
> Robert Weber wrote:
> 
> Before I report this as a "bug" in bind 8, I'd like to run my configs by
> everyone first:

Paul Vixie sent out a couple of BIND 8 announcements last month which
had the following item in the CHANGES document:

1225.    [bug]           don't send cross class additional records.

Here are the summaries:
.......................................................................
BIND 8.2.5 is a maintainance release of BIND 8.2, containing minimal
changes from 8.2.4.

Highlights vs. BIND 8.2.4:

        Minor bug fixes and portability changes.

the distribution files are:

ftp://ftp.isc.org/isc/bind/src/testing/825-t1a/bind-src.tar.gz
ftp://ftp.isc.org/isc/bind/src/testing/825-t1a/bind-doc.tar.gz
ftp://ftp.isc.org/isc/bind/src/testing/825-t1a/bind-contrib.tar.gz
.......................................................................
BIND 8.3.0 is the first release of 8.3, and contains new features not
found in 8.2.5.

Highlights vs. BIND 8.2.5:

        Minor bug fixes and portability changes.
        Some new resolver API elements.
 Improved operational reporting.
 Can now AXFR unknown RR types (in, out, or both).
 IPv6 transport support in the resolver (from KAME).

the distribution files are:

ftp://ftp.isc.org/isc/bind/src/testing/830-t1a/bind-src.tar.gz
ftp://ftp.isc.org/isc/bind/src/testing/830-t1a/bind-doc.tar.gz
ftp://ftp.isc.org/isc/bind/src/testing/830-t1a/bind-contrib.tar.gz
.......................................................................

HTH,

Andris Kalnozols
Hewlett-Packard Laboratories
andris at hpl.hp.com