Hello Noel Butler,
Am 2012-02-18 11:25:10, hacktest Du folgendes herunter:
If the OP is trying to avoid inline editing, does not the above become
pointless?
Yes, and the wish of the OP is my wish too!
Still requires inline editing to remove the
include /path/to/etc/zone1.conf, else named
While not _exactly_ what was asked for, rndc addzone and rndc
delzone seem to be able to do what you want...
Just an idea..
AlanC
--
a...@clegg.com | 1.919.355.8851
signature.asc
Description: OpenPGP digital signature
___
Please visit
Hi,
In a recent discussion on another list, it was discussed the pros and
cons of splitting the main conf file to a per domain.
In binds case it would be to /etc/named.d/*.conf
So each zone would have a file in that directory containing only the
relevant info
eg:
zone example.com {
Yes, it's quite possible to split named.conf into separate per-zone .conf files
and then 'include' them back into named.conf. You can even put the list of
include statements in a separate file, and then include that into named.conf.
named.conf:
options {
[...]
}
include
+1 to all of Chris' suggestions, especially the bit about including one
file in named.conf, and including the per-zone files in that file. Makes
it much easier to update that file with a script, or what have you.
hth,
Doug
On 02/17/2012 07:11, Chris Buxton wrote:
Yes, it's quite possible to
On Fri, 2012-02-17 at 07:11 -0800, Chris Buxton wrote:
Yes, it's quite possible to split named.conf into separate per-zone .conf
files and then 'include' them back into named.conf. You can even put the list
of include statements in a separate file, and then include that into
named.conf.
6 matches
Mail list logo
