29 Pro
2013
29 Pro
'13
10:03
Hi Johan & Anand,
we definitely plan to add the templating to the config.
Ondrej
--
Ondřej Surý -- Chief Science Officer
-------------------------------------------
CZ.NIC, z.s.p.o. -- Laboratoře CZ.NIC
Americka 23, 120 00 Praha 2, CZE
mailto:ondrej.sury@nic.cz http://nic.cz/
tel:+420.222745110 fax:+420.222745112
-------------------------------------------
On 29. 12. 2013, at 1:37, Johan Ihrén
<johani(a)johani.org> wrote:
Hi Anand and Knot-team,
On Dec 23, 2013, at 18:23 , Anand Buddhdev
wrote:
The Knot zones directive allows some options at the top-level (such as
"storage", "disable-any", etc). However, the following options can
only
be specified per zone:
xfr-in
xfr-out
notify-in
notify-out
update-in
Could you make it so that these options can also be specified at the top
level so that all zones specified after can inherit the same options.
This is useful when I have the same master or set of masters for a whole
bunch of zones, and I don't need to specify them each time for each zone
separately.
While fully supporting Anand in the need to avoid having to specify the same set of
masters (or slaves) over and over I must say that I find the "pattern:"
mechanism of NSD4 much more powerful than just a mechanism for "global" values.
I.e. I would like to be able to:
1. inherit from a named entity, not just whatever was specified just above. The latter
potentially requires me to reorganize my entire config when masters change, not good.
Inheriting from something with a name gets rid of that limitation.
2. have multiple "sets" of settings that are inherited, i.e. if I have 100
customers (masters), each with multiple zones, then I'd like to define some sort of
"group" or "template" for each, and then reuse that for all zones
associated with that template.
And now back to the holidays... ;-)
Johan
_______________________________________________
knot-dns-users mailing list
knot-dns-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users