slave to slave zone transfer

Joseph S D Yao jsdy at cospo.osis.gov
Thu Aug 31 23:39:03 UTC 2000


On Thu, Aug 31, 2000 at 05:28:39PM +0100, Quadri, Jay wrote:
> Assume a domain called zzz.com on a remote site,  there are also subdomains
> called aaa.zzz.com & bbb.zzz.com & ccc.zzz.com (slave to zzz.com) all
> sitting on differ site.  The Master domain zzz.com is also a remote slave on
> aaa.zzz.com, bbb.zzz.com & ccc.zzz.com.  
> 
> zzz.com receive aaa.zzz.com, bbb.zzz.com & ccc.zzz.com zone files.  Thus On
> zzz.com I can resolve hostnames located on aaa.zzz.com, bbb.zzz.com &
> ccc.zzz.com.
> 
> As a client with bbb.zzz.com in my resolve.conf file, why can't I resolve
> hosts names located on aaa.zzz.com,  I would have thought that since I set
> up zzz.com to be slave on bbb.zzz.com everything would be alright.  The
> zzz.com zone file itself gets transferred to bbb.zzz.com, but aaa.zzz.com, &
> ccc.zzz.com. doesn't, i.e. , I can resolve ccc.zzz.com itself, but not the
> hosts within it.  Can you think why the subdomain zones file doesn't get
> transferred to the other subdomains.  
> 
> The zone file of zzz.com contains A & NS for aaa.zzz.com, bbb.zzz.com &
> ccc.zzz.com.

All those zzz's just about put me to sleep.

The above doesn't make a lot of sense.  I suspect that you need to be
told the same thing as several other people this week.  New zones are
not automatically propagated to name servers that just happen to be
slaves for other zones.  You have to manually insert the zones into the
named.conf files.  After all, I just might want to make the A server
the only slave for the A zone, the B server for the B zone, and so
forth.  Or I might want to make the A, B, and C servers the MASTERS -
this is actually the more common case! - and the Z server the slave to
each of them!

Decide what you want to do, then tell the servers to do it - don't
assume that they'll read your mind.  ;-)

-- 
Joe Yao				jsdy at cospo.osis.gov - Joseph S. D. Yao
COSPO/OSIS Computer Support					EMT-B
-----------------------------------------------------------------------
This message is not an official statement of COSPO policies.



More information about the bind-users mailing list