authority ok, but named-xfer won't go

[Mark.Andrews at nominum.com]

> 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

	212.49.89.10 is not configured as the master for filmafricana.co.ke.
	The answer above reflects a referral to the ke servers.
> 			
> 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

	212.49.89.10 has a syntax error in the zone file for als.co.ke.
> 
> 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.

	But is the "aa" (Authoratative Answer) flag set in the answers
	to the following queries:

	dig +norec filmafricana.co.ke soa @212.49.89.10
	dig +norec als.co.ke soa @212.49.89.10

	The lines above are a summary of the respones to those two queries.
> 
> 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.

	Fix the errors logged on the master.
> 
> Len
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com