Hi Matthias-Christian,
thanks for giving us a try! The reasoning behind naming each interface
was mainly to stay consistent with the "remotes" section. But to be honest,
there's not much added value in doing that, other than allowing user
to specify 'via' for a remote using a symbolic name. If we would allow multiple
interfaces per name, Knot wouldn't able to tell which interface did you mean.
Downside is that it gets tedious when you have many interfaces (and/or
using dual stack).
But we talked recently about making the configuration user friendly
and general idea is to
stop naming interfaces (thus reducing clutter) and allowing multiple
addresses for remotes.
Or make groups of remotes, but you get the idea.
We're still weighing the options, so I find your remarks very valuable :)
Kind regards,
Marek
--
Marek Vavruša Knot DNS
CZ.NIC Labs
http://www.knot-dns.cz
-------------------------------------------
Americká 23, 120 00 Praha 2, Czech Republic
WWW:
http://labs.nic.cz http://www.nic.cz
On 24 January 2013 02:43, Matthias-Christian Ott <ott(a)mirix.org> wrote:
I just successfully migrated a several zones from NSD
to Knot DNS. The
migration was straightforward and quick, but I limiting the number of
addresses per interface and remote server to one doesn't make sense to
me especially with dual stack hosts. This is more intuitive to me in
NSD. What is the rationale behind the current syntax?
Regards,
Matthias-Christian
_______________________________________________
knot-dns-users mailing list
knot-dns-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users