authority ok, but named-xfer won't go

[Len Conrad]

On a slave ns console:

May 18 12:29:45 as1 named-xfer[2736]: [212.49.89.10] not authoritative for 
filmafricana.co.ke, SOA query got rcode 0, aa 0, ancount 0, aucount 3
			
May 18 12:29:58 as1 named-xfer[2735]: [212.49.89.10] not authoritative for 
als.co.ke, SOA query got rcode 0, aa 0, ancount 1, aucount 2

The above two console msgs appear on as1.meiway.com, that is slave for 
these two domains that are mastered by webstar.skyweb.co.ke.  As a result, 
when webstar notifies as1, as1 does not perform the axfr.

All digs I do for these two domains return webstar and as1 as the 
authoritative ns's, including webstar as the SOA for both.

What is bothering as1 so that it can no longer find webstar/212.49.89.10 as 
authoritative?

btw, as1 does already have the db. zone files for both domains so at some 
point the axfr's were running fine.  it just the zone updates after notify 
that are now failing.

Len