Incorrect processing of IPv6 dynamic updates

[Kevin Oberman]

I am seeing a problem with BIND 8.1.2 with the zone files saved after
dynamic updates from an IPv6 system. I don't know if the problem is
with the IPv6 implementation (Compaq) or BIND.

The problem is that a large negative number (-429496730) is appearing
in the TTL field for these records. This causes BIND to report an
unrecognized record type.

I see no errors logged when the update is made and PTR record resolves
correctly, but the number then appears in the file. Even if the Compaq
system is providing an invalid update, I would expect an error then
and not when named is restarted.

Is this a problem anyone else has seen? If V8.2.1 fixes this, I guess
I'll have the incentive to upgrade.

Thanks,
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest Orlando Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman at es.net				Phone: +1 510 486-8634