Bind 9 Slave Server Not Receiving Updated Zone

[Nate D.]

I have two DNS servers, a master and a slave, both running
bind-9.2.1-1.7x.2 on Redhat 7.3. Both servers are configured with two
RFC1918 IP addresses. I am using multiple views on both servers, and
properly using transfer-source & query-source between the two servers'
multiple IP addresses to split the zone transfers properly between
views.

If I create a new zone on the master server and reload, and then
create a new slave zone on the slave server and reload, the zone
transfer works.

Here's a description of my problem:

When I make a change to a zone on the master server (in either view),
and run rndc reload, the changes become active. However, when I run
rndc reload on the slave server, the slave server does not receive the
updated zone.

The only way that the slave server receives the zone is if I restart
bind itself using '/etc/init.d/named restart'.

When I run 'ndc reload' on the slave, I don't see any queries in the
master server's log. However, when I restart bind on the slave server,
I see the SOA queries & the axfr request in the master server's log,
and the axfr for the zone that changed in the slave server's log.

I've gone so far as to use 'notify explicit' and 'also-notify' with
the IP of my slave server, and that doesn't seem to work.

I can duplicate this scenario every time.

Anyone have any ideas off the top of their head? If not, I'd gladly
supply my config & logs.

Regards,

Nate D.