notify option does not work in Bind 9.x, is this a known bug?

[Steven Job]

Having a problem when you set "notify explicit;" or "notify yes;" with a
"also-notify" statement (either globally or per zone).

If you have a few domains then it is fine.  Will send the notifies as expected.
But if you have several thousand domains Bind will no longer send out any
notifies.  Not quite sure where the number of zones are that is stops working. 
But it definately does not work around the 50k limit. You just end up having to
wait for the SOA refresh value.

Saw postings about this since Oct 30 2003.  Is this a known bug?

You get this (no notify is sent):
Feb 20 10:10:55.304 client 192.168.1.7#65030: update 'samplezone.com/IN'
approved
Feb 20 10:10:55.304 client 192.168.1.7#65030: updating zone 'samplezone.com/IN':
adding an RR
Feb 20 10:10:55.304 writing to journal
Feb 20 10:10:55.306 client 192.168.1.7#65030: send
Feb 20 10:10:55.306 client 192.168.1.7#65030: sendto
Feb 20 10:10:55.306 client 192.168.1.7#65030: senddone
Feb 20 10:10:55.306 client 192.168.1.7#65030: next
Feb 20 10:10:55.306 client 192.168.1.7#65030: endrequest
Feb 20 10:10:55.306 client @0xc14ae88: udprecv
Feb 20 10:10:55.306 zone_timer: zone samplezone.com/IN: enter
Feb 20 10:10:55.306 zone_maintenance: zone samplezone.com/IN: enter



But if you do not specify any notify option you will get it working properly.
Feb 20 10:13:18.083 client 192.168.1.7#51283: update 'samplezone.com/IN'
approved
Feb 20 10:13:18.083 client 192.168.1.7#51283: updating zone 'samplezone.com/IN':
adding an RR
Feb 20 10:13:18.083 writing to journal
Feb 20 10:13:18.086 client 192.168.1.7#51283: send
Feb 20 10:13:18.086 client 192.168.1.7#51283: sendto
Feb 20 10:13:18.086 client 192.168.1.7#51283: senddone
Feb 20 10:13:18.086 client 192.168.1.7#51283: next
Feb 20 10:13:18.086 client 192.168.1.7#51283: endrequest
Feb 20 10:13:18.086 client @0xb6b2050: udprecv
Feb 20 10:13:18.087 zone_timer: zone samplezone.com/IN: enter
Feb 20 10:13:18.087 zone_maintenance: zone samplezone.com/IN: enter
Feb 20 10:13:18.087 zone samplezone.com/IN: sending notifies (serial 2003010106)
Feb 20 10:13:18.087 dns_adb_destroyfind on find 0x1991c1c8
Feb 20 10:13:18.112 dns_adb_destroyfind on find 0x1991c1c8
Feb 20 10:13:18.112 dns_adb_destroyfind on find 0x1991c1c8
Feb 20 10:13:18.112 dns_adb_destroyfind on find 0x1991c1c8
Feb 20 10:13:18.112 zone samplezone.com/IN: sending notify to 192.168.1.11#53



Here is a sample primary named.conf:
acl "secdns" { 127.0.0.1/32;  192.168.1.0/24; };

options {
        version "A great version";
        directory "/var/named";
        pid-file "/var/named/named.pid";
        // Server will attempt to do all work required to answer query.
        recursion no;
        allow-query { any; };
        allow-transfer { "secdns";};
        blackhole { none; };
        provide-ixfr yes;
        request-ixfr yes;
        tcp-clients 1000;
        transfers-per-ns 1000;
        transfers-out 2000;
        notify explicit;
        notify-source 192.168.1.100;
        also-notify { 192.168.1.11; 192.168.1.12; 192.168.1.13; 192.168.1.14;
192.168.1.15; 192.168.1.16; 192.168.1.17; 192.168.1.18; };
};
zone "." { type hint;
         file "named.root";
};
include "/etc/zones.conf";