origin defaulting to undesired domzin in zone file transfer to slave

[Barry Margolin]

In article <bhbcc9$3ov$1 at sf1.isc.org>,
Bill F  <__billf at lfnetworking.com> wrote:
>Sorry, I'm not sure I understand.
>The slave transfers the zone file from the master when it starts.
>That's the correct mechanism, isn't it?  Slave status is properly 
>defined in named.conf, isn't it?

The problem is that you list the same "db.operon" filename for operon.net
and operon.com on the slave server.  As a result, after it transfers
operon.net into the file, it then overwrites it with operon.com (or the
other way around).

On a slave server you *must* use a different file for each zone.

>
>Mark_Andrews at isc.org wrote:
>> 	You cannot share master files for slave or dynamic master zones.
>> --
>> Mark Andrews, Internet Software Consortium
>> 1 Seymour St., Dundas Valley, NSW 2117, Australia
>> PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at isc.org
>> 
>
>
>


-- 
Barry Margolin, barry.margolin at level3.com
Level(3), Woburn, 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.