maintaining record consistency in two views

Barry Margolin barmar at alum.mit.edu
Tue Dec 20 20:08:52 UTC 2005


In article <do9d4h$2llh$1 at sf1.isc.org>,
 "Frank Y.F. Luo" <luoy at muohio.edu> wrote:

> I am attracted to the view feature for our internal and external network but
> find it is not convenient to maintain two zone (in two separate views
> though) for a lot of command records. I was advised to use sortlist feature
> instead for the same purpose but that reveal the association between our
> internal and external network.
> 
> I am wondering how I can make a request for failover feature for view. Let
> me elaborate this a bit
> 
> say view X and Y, both having abc.com zone, serving internal and external
> network separately. The current RFC requires that you have to maintain
> abc.com zone in view X and Y seperately. So if you have a common entry like
> www.abcd.com, you have maintain the same record in two places. I am
> wondering if I can just define it in one view, say Y, and any query against
> X will fail over to view Y since in X there is no www.abcd.com record.

How about using an include file.  Put all the common records in that 
file, and then the per-zone files can use "$INCLUDE zone.common.db" to 
incorporate these records.

-- 
Barry Margolin, barmar at alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***



More information about the bind-users mailing list