How to set a fixed EDNS Client Subnet when using policy.FORWARD?

[GubernievS]

How to include a fixed EDNS Client Subnet (e.g., 1.2.3.0/24) for all queries sent via that forward policy in Knot Resolver 5.7.6?

Thanks!

[vcunat]

We do not have any way of sending any EDNS Client Subnet so far.

[GubernievS]

Maybe there’s a hack to insert a fixed subnet as text into the DNS request?

[vitalik6243]

I support implementing at least a method for passing EDNS in a similar way to dig @8.8.8.8 domain.com +subnet=ip_address
Because kresd at the current stage strips all subnet information

[vcunat]

Yes, we send nothing. The other side will then use the outgoing IP address instead of the sent client-subnet.

[GubernievS]

The external IP address of the server with knot-resolver is detected incorrectly by the upstream DNS servers, so the returned IPs belong to a different region.
Sending a fixed client subnet in the EDNS option would solve this problem.