Hello Shawn,
root@DFW01-CPS01:~# dig @localhost +subnet=52.57.28.138 morpheus-ien.insnw.net
local-address=127.0.0.1
dig asks ::1 if available!
Try
dig @127.0.0.1
or
local-address=127.0.0.1,::1
--
Winfried
___
Pdns-users mailing list
Pdns-user
> On Aug 3, 2017, at 1:23 PM, Remi Gacogne wrote:
>
> On 08/03/2017 07:38 PM, Shawn Zhou wrote:
>> Your explanation makes sense but that still doesn't explain the original
>> problems I see with pdns. see [1]. When pdns received the response for
>> the 1st query, it should have a cache entry for
On 08/03/2017 07:38 PM, Shawn Zhou wrote:
> Your explanation makes sense but that still doesn't explain the original
> problems I see with pdns. see [1]. When pdns received the response for
> the 1st query, it should have a cache entry for scope prefix-length of
> 16 (btw, why don't I have that inf
Hi,
On 08/03/2017 09:37 PM, Charles Sprickman wrote:
> FWIW, “trace-regex” gave me an error, so I just did a full trace and
> then cleaned up the results.
>
> https://gist.github.com/sporkman/1b1b01a3b33ca3e2029728cb90a1eee8
>
>> We can then find out the problem for you, or perhaps you see it al
> On Jul 29, 2017, at 5:19 AM, bert hubert wrote:
>
> On Sat, Jul 29, 2017 at 12:19:11AM -0400, Charles Sprickman wrote:
>> Here’s a few things I’ve tried:
>>
>> - Verify with DNSVIZ: http://dnsviz.net/d/dot.nyc.gov/dnssec/
>> - Update PowerDNS to powerdns-recursor-4.0.6
>> - Remove “scrub” ru
Your explanation makes sense but that still doesn't explain the original
problems I see with pdns. see [1]. When pdns received the response for the 1st
query, it should have a cache entry for scope prefix-length of 16 (btw, why
don't I have that information when I dig against pdns?). When the 2n
On 08/03/2017 12:04 AM, Shawn Zhou wrote:
> 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 d
