bind 8.2.2p3 + patch4 still showing error multiple SOA
Randall J. Wormser
nospam at me
Fri Nov 12 16:05:00 UTC 1999
We have a primary and a slave; both are ULTRA-2170 systems running
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
Transfers for corresponding in-addr.arpa zones work fine.
And, yes; I did try removing the zone file on the slave server.
On 12 Nov 1999 07:26:28 -0800, Barry Margolin <barmar at bbnplanet.com>
>In article <80fooc$ni1$1 at nnrp1.deja.com>, <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
>Did you delete the zone files on the slave server after fixing the code?
>The broken named-xfer was writing bad zone files, so you need to remove
>them to force them to be updated.
More information about the bind-users