bind 9.12.3-P1 dies after change of IP on outbound interface

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Lateley I realise some strange behaviour of the recent dns/bind912 port.

Running named (9.12.3-P1) on a 12-STABLE gateway/router/firewall with outbound interface
tun0 to our privider, named seems to crash since the last port upgrade whenver the ISP is
changing the IP (using ppp with some linkup/linkdown scripts due to IPv6, nothing fancy).

The last sign of live named provides is shown below:

[...]
Dec 20 13:22:46 <3.2> gate named[1120]: socket.c:3251: REQUIRE(sock->references == 1)
failed, back trace Dec 20 13:22:46 <3.2> gate named[1120]: #0 0x2c8880 in ??
Dec 20 13:22:46 <3.2> gate named[1120]: #1 0x4b111a in ??
Dec 20 13:22:46 <3.2> gate named[1120]: #2 0x4e35fc in ??
Dec 20 13:22:46 <3.2> gate named[1120]: #3 0x4e9e79 in ??
Dec 20 13:22:46 <3.2> gate named[1120]: #4 0x35554d in ??
Dec 20 13:22:46 <3.2> gate named[1120]: #5 0x354a2f in ??
Dec 20 13:22:46 <3.2> gate named[1120]: #6 0x4d49fa in ??
Dec 20 13:22:46 <3.2> gate named[1120]: #7 0x800dc37c6 in ??
Dec 20 13:22:46 <3.2> gate named[1120]: exiting (due to assertion failure)
Dec 20 13:46:59 <3.5> gate named[3195]: starting BIND 9.12.3-P1 <id:cfdd35f>

Prior to the last update of dns/bind912, this router/firewall appliance was running more
than a month without having such trouble, even the ISP is randomly changing the IPv4/IPv6
addresses spread over the day.

What is wrong?

Kind regards,

O. Hartmann


- -- 
O. Hartmann

Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQSy8IBxAPDkqVBaTJ44N1ZZPba5RwUCXBuVPgAKCRA4N1ZZPba5
RxB8AQDwXm7hVifhDP841aGckXLCCino95lSAtHNLoOz2nBcowD9F4lUyflB/Imq
OvERuSNKeixaDDazKj6KJfNtiE8/0gU=
=H6r2
-----END PGP SIGNATURE-----