named-xfer and multiple SOA RRs

[Barry Margolin]

In article <000201bf304e$7107eb70$1ad174c2 at pcnew.inrete.it>,
Marco Meinardi <marcom at inrete.it> wrote:
>When the named-xfer of the bind 8.2.2 transfer the zones for those domains,
>I get a file with the dns configuration for each domain, but this file
>contains 2 SOA records (one on the beginning and another at the end), even
>if the original file on the primary NS contains one SOA record only.
>Multiple SOA records are rejected by named and it doesn't load the zone
>unless I manually remove the redundant SOA record at the end of the config
>file.
>How can I solve this problem?

This is a bug that was reported by about a dozen other people in this
newsgroup last week, and a patch was posted.  You should upgrade to
patchlevel 5.

Once you do this, you'll need to remove all the zone files that were
written on the secondary server by the broken version.

-- 
Barry Margolin, barmar at bbnplanet.com
GTE Internetworking, Powered by BBN, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.