Hi Chuck,
you can use branch ecs-pach:
https://gitlab.labs.nic.cz/labs/knot/tree/ecs-patch
https://gitlab.labs.nic.cz/labs/knot/commit/9fe76fe7dad761b05863e94cf36cf7c87c7ac688
It responses with scope prefix length of zero only to query with ECS.
Regards,
Vita
Dne 17.2.2017 v 07:52 Chuck Musser napsal(a):
On Feb 15, 2017, at 4:17 AM, Vítězslav Kříž <[email protected]> wrote:
Hi Chuck,
I have some questions about what you exactly need to support.
Do you want to include ECS to every response or only to responses which
contains ECS in query?
Only responses that contain it in the query. It’s probably wise to only
send it in response to servers that appear able to use the information
and are likely to include ECS on subsequent requests.
Do you want to response with same Client Subnet used in query or always use
Client Subnet with prefix length of 0?
I think client subnet, with scope prefix length of zero. The intent is to
indicate that the
feature is supported but isn’t being used to (yet anyway) to tailor the
response.
Chuck
_______________________________________________
knot-dns-users mailing list
[email protected]
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users
