On 7/12/19 6:01 PM, Brian Candler wrote:
> On 12/07/2019 22:03, Bryan Fields wrote:
>> $ dig 50121.nodes.allstarlink.org @44.98.254.151 if you want to see it fail.
>
> Works for me:
Well crap, must be a packet molester on my ISP, right?
> Are you sure you don't have some sort of DNS-inspecting f
On 12/07/2019 22:03, Bryan Fields wrote:
$ dig 50121.nodes.allstarlink.org @44.98.254.151 if you want to see it fail.
Works for me:
$ dig 50121.nodes.allstarlink.org @44.98.254.151
; <<>> DiG 9.10.6 <<>> 50121.nodes.allstarlink.org @44.98.254.151
;; global options: +cmd
;; Got answer:
;; ->>H
On 7/12/19 3:18 PM, Bryan Fields wrote:
> I have an authoritative server with an A record set as 0.0.0.0 and pdns is not
> serving this up. I'm not getting a SRVFAIL or any message, it's just timing
> out waiting for a response.
>
> I don't see any errors in the logs either, with it turned up to
I have an authoritative server with an A record set as 0.0.0.0 and pdns is not
serving this up. I'm not getting a SRVFAIL or any message, it's just timing
out waiting for a response.
I don't see any errors in the logs either, with it turned up to 10.
Is this correct behavior? If so where is it m
Hello,
thank you all for the information, and yes, i will need to read the
documentation again. I have a clearer idea now of how the dnssec database is
working.
greetings,
Philip
Op 12/07/19 om 08:25 schreef frank+pdns--- via Pdns-users:
On 11 Jul 2019, at 16:57, Philip Vanmontfort
mailto
