It would be a nice feature, but in lieu of that, you could always
have a script manage your named.conf and incorporate the
variable-substitution logic into that. If you want to go Old School,
use cpp, make, sccs, some of those long-forgotten tools :-)
I've had wonderful success with Makefile(s)
> On 1 Apr 2015, at 23:30, Jeff Sadowski wrote:
>
> Do I really need to have each zone with its own file?
You can omit the file option in a slave zone and named will keep the zone in
memory only. The disadvantage is it will have to retransfer all the zones in
full when it starts before it can
:-)
- Kevin
-Original Message-
From: bind-users-boun...@lists.isc.org
[mailto:bind-users-boun...@lists.isc.org] On Behalf Of Barry Margolin
Sent: Wednesday, April 01, 2015 10:09 PM
To: comp-protocols-dns-b...@isc.org
Subject: Re: Variable in name
On Thu, Apr 2, 2015 at 11:09 AM, Jeff Sadowski wrote:
> On Wed, Apr 1, 2015 at 8:09 PM, Barry Margolin wrote:
>> In article ,
>> Jeff Sadowski wrote:
>>
>>> I have a number of slave domains that I would like a naming scheme and
>>> not have to go to each and change the filename.
>>>
>>> I have
On Wed, Apr 1, 2015 at 8:09 PM, Barry Margolin wrote:
> In article ,
> Jeff Sadowski wrote:
>
>> I have a number of slave domains that I would like a naming scheme and
>> not have to go to each and change the filename.
>>
>> I have the following zones
>>
>> zone "1.168.192.in-addr.arpa" {
>>
In article ,
Jeff Sadowski wrote:
> I have a number of slave domains that I would like a naming scheme and
> not have to go to each and change the filename.
>
> I have the following zones
>
> zone "1.168.192.in-addr.arpa" {
> include "named.slave";
> };
> zone "2.168.192.in-addr.arpa"
6 matches
Mail list logo
