Hello,
I am testing ecs support using unbound 1.6.4 and I face the same problem that
another user reported back in May 6, 2015.
I have a CNAME record that is managed by my own authoritative that has edns
support and with expected scope prefix-length (/16 as in my example [1]) and
that record
On 5/8/15, 1:23 AM, Yuri Schaeffer y...@nlnetlabs.nl wrote:
At this point Unbound has a CNAME that is ECS specific and an A
that is not. It will use the 0 scope for the CNAME as well as the A
and cache the response.
Well, you say that. But the trace shows that the A answer was in fact
ECS
