Known Bug question

[Kevin Darcy]

Oh, the problem exists all right. Look in the master's zone (i.e. "dump")
file. The delegations are gone. You can't tell that this happening just by
querying the master, since it's answering with the child's NS records.

Note, however, that this problem is somewhat benign
*AS*LONG*AS*YOU*STAY*AUTHORITATIVE* for the child zone, since BIND 8 mixes
glue (i.e. it'll happily serve up the child's NS records in a zone transfer
of the parent zone). However, if you ever *stop* being authoritative for the
child zone, you've got a nasty surprise waiting for you: you have no
authoritative NS records and no delegations either, so effectively the child
zone disappears off the face of the earth. Evil stuff.


- Kevin

Ian Watts wrote:

> I have a question about the following bug, documented in the file
> "INSTALL" in the BIND 8.2.4 distribution.
>
> <excerpt>
> Known Dynamic DNS Bugs
>
>         If the server is master for a zone and authoritative for a child
> of that zone, then a dynamic update to the parent will destroy the
> delegation to the child when the parent zone is written to disk.  This
> problem will be fixed in a future release.  The only workaround is to not
> be authoritative for child zones of a dynamic zone.
> </excerpt>
>
> I haven't observed this behavior myself, even when making dynamic updates
> to a zone that has both dynamically updatable and non-updatable child
> zones.  Is there something I missed or is it that it only applies under a
> specific set circumstances?  Note that I never add NS records dynamically.
> Also, this is a one-server arrangement without a slave server (though I
> can't see that it would matter).
>
> Can anyone clarify this?
>
> -- Ian Watts