I don't think that's the right behavior. If Client Subnet scope set to 0,
resolver should not cache it.unbound DNS gives me the expected output as it
cache has different entries for different client subnet. Why is pdns recursor's
implementation different?
root@DFW01-CPS02:~# dig @localhost +subn
Hi Shawn,
On 08/02/2017 08:47 AM, Shawn Zhou wrote:
> Sorry. I meant the authoritative nameserver did respond with the correct
> answer.
The authoritative server answers with a EDNS Client Subnet scope set to
0 when we send a query with a source set to 127.0.0.1/32, meaning that
we can cache th
