origin defaulting to undesired domzin in zone file transfer to slave

[Bill Friedman]

>   Thanks. I altered named.conf on slave as follows...
>
> zone "operon.com" in {
>         type slave;
>         file "bak.operon.com";
>         masters { ####; };
> };
>
> zone "operon.net" in {
>         type slave;
>         file "bak.operon.net";
>         masters { ####; };
> };
>
> zone "qiagenoperon.com" in {
>         type slave;
>         file "bak.qiagenoperon.com";
>         masters { ####; };
> };
>
>
> ok, now I get three zone files that contain the appended domains and 
> the $ORIGIN reference as follows.  
>
> $ORIGIN .
> $TTL 86400      ; 1 day
> .....
> $ORIGIN qiagenoperon.com.   # operon.com. and operon.net. in those 
> zone files on slave
>
> One entry that's different is the mx record for kenny in the 
> operon.com file in which the domain is stripped, however, I guess 
> since it's transferred with the operon.com zone that will be appended 
> in the transfer process, no?
>
> master
>
>                         MX      150 kenny.operon.com.
>
> slave
>
>
>                         MX      150 kenny
>
>
> Barry Margolin wrote:
>
>>In article <bhbcc9$3ov$1 at sf1.isc.org>,
>>Bill F  <__billf at lfnetworking.com> wrote
>>    
>>
>>>    
>>>
>>
>>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).
>>
>>  
>>
>