bind 8.2.2p3 + patch4 still showing error multiple SOA

[Mark_Andrews at iengines.com]

> We have a primary and a slave; both are ULTRA-2170 systems running
> Solaris 2.6.
> 
> Following the upgrade from 8.1.2-t3b to 8.2.2p3 + the patch4.txt,
> named-xfer on the slave fails with:
> 
> [ ip address of primary ] not authoritative for my.zone.com,    SOA
> query got rcode 0, aa 0, ancount 1, aucount 0 

	Fix the syntax error for this zone on the primary.  The error
	will have been logged.  If you can't find the error touch the
	zone file and reload.

	Mark
> 
> transfers for corresponding in-addr.arpa zones work fine.
> 
> On 11 Nov 1999 17:07:02 -0800, bleve at my-deja.com wrote:
> 
> >
> >
> >I have two DNS servers, both now running 8.2.2p3 + the patch4.txt
> >patch to named.xfer.c
> >
> >they're both solaris boxes, one is solaris 7 + IPv6, one is
> >solaris 2.6, both are SPARCservers
> >
> >Despite the updated named-xfer (and lots of ndc stop; ndc start,
> >killing & starting named by hand etc), although my master is
> >logging no errors, the slave is still reporting multiple SOA
> >records and refusing to load the zones it is a secondary
> >for.
> >
> >Before I go into huge detail about how I have patched named-xfer.c
> >(replaced > with >= and recompiled .. "duh"), is anyone else
> >seeing this problem?
> >
> >
>
> >Sent via Deja.com http://www.deja.com/
> >Before you buy.
> 
> 
--
Mark Andrews, Internet Engines Inc. / Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at iengines.com