>
> Duncan Campbell wrote:
> > i have a copy of the ARM here, but can't find in
> > it any mention of syntax allowing use of variables
> > in named.conf.
> >
> > i'd like to do something like:
> >
> > #define cust1-ns '1.2.3.4; 1.3.4.5'
> > or
> > ns.cust1.com='1.2.3.4; 1.3.4.5'
> >
> > and later
> >
> > zone zone1 {type=slave; file="slave/zone1"; masters {cust1-ns;};};
> > zone zone2 {type=slave; file="slave/zone2"; masters {cust1-ns;};};
> >
> > or
> >
> > zone zone1 {type=slave; file="slave/zone1"; masters {$ns.cust1.com;};};
> > zone zone2 {type=slave; file="slave/zone2"; masters {$ns.cust1.com;};};
> >
> > does anything like this exist in the parser?
>
> The acl statement can define a symbolic name for an address match list.
> If you don't need anything outside of that context, try using them.
>
> -Robert
ACLs cannot be used where a address list is required.
The masters clause takes an address list.
Mark
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews@xxxxxxx
|
