Issues with DNS NOTIFY using BIND 9.1.3

[Vinson Armstead - PA]

After making a change to the zone files on my master server I restart BIND
(kill  -HUP ???). I check my slave server it does not seem to have received
the DNS NOTIFY sent from the master. The zone files on the secondary are not
updated and do not update until the TTL expires or I restart BIND (kill
-HUP).

I check the log files on the master (configure using the logging feature)
and see the following :

Notify.log
Aug 28 14:46:34.438 notify: debug 3: zone 0.0.127.in-addr.arpa/IN: queueing
notifies
Aug 28 14:46:34.515 notify: debug 3: zone 1.168.192.in-addr.arpa/IN:
queueing notifies
Aug 28 14:46:34.522 notify: debug 3: zone domain1.com/IN: queueing notifies
Aug 28 14:46:34.531 notify: debug 3: zone domain2.com/IN: queueing notifies

Security.log
Aug 28 14:52:08.231 security: debug 3: client 10.131.149.36#1140: request
has valid signature
Aug 28 14:52:08.265 security: debug 3: client 10.131.149.36#1140: recursion
approved
Aug 28 14:52:08.266 security: debug 3: client 10.131.149.36#1140: query
approved

The dates of the log files on the slave are not updated...


What I expect to happen is that the master send the DNS NOTIFY message to
the slave and the slave then performs a zone x-fer to update its
information. Thanks dose not seem to be happening...the question is why????

Any suggestion would be appreciated

thanks 
> Vinson Armstead
> E-mail:  Vinson_Armstead at gmacm.com
> 
>