9 Říj
2018
9 Říj
'18
10:48
Hello,
we did not have time to solve this yet so it is not supported at the moment.
You can add yourself to
https://gitlab.labs.nic.cz/knot/knot-resolver/issues/368
and you will be notified once it changes.
Let me add that right now we are in middle of refactoring and do not
have capacity to solve this ourseles but patches are welcome - we will
review.
Workaround could be to run two instances where each binds to different
IP address.
Please direct further communication about Knot Resolver to its mailing
list https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-resolver-users .
Thank you for understanding.
Petr Špaček @ CZ.NIC
On 09/10/2018 10:11, Antti Ristimäki wrote:
Hi,
Is it possible to restrict DNS64 module only for specific IPv6 subnets
in Knot Resolver? The reasoning behind this is that this would make it
possible to run DNS64 resolver on the same instance with the "normal"
resolver in a way that fake AAAA records are returned only to IPv6-only
clients whereas normal dual-stack or IPv4-only clients are served with
unmodified A records.
I found an issue [1] that seems to be related to the very same thing,
but I was left a little bit uncertain what the current situation is and
how this should/could be configured.
[1] https://gitlab.labs.nic.cz/knot/knot-resolver/issues/368
Cheers,
Antti