On Tue, Aug 28, 2018 at 09:44:38AM -0700,
David Conrad wrote
a message of 161 lines which said:
> On September 5 2017, we’ve published
> https://www.icann.org/dns-resolvers-checking-current-trust-anchors
Thanks, I did not notice it. Very useful.
> If this is incomplete, please let us know.
Stephane,
On September 5 2017, we’ve published
https://www.icann.org/dns-resolvers-checking-current-trust-anchors
If this is incomplete, please let us know.
Thanks,
-dc
> On Aug 28, 2018, at 3:05 AM, Stephane Bortzmeyer via Unbound-users
> wrote:
>
> I'm compiling a list of commands to
Stephane Bortzmeyer via Unbound-users writes:
> Thanks, but it seems to work with very recent Unbounds only (the one
> in Debian stable, or the one in Ubuntu LTS reply REFUSED).
Unbound 1.6.2, 24 april 2017:
Add trustanchor.unbound CH TXT that gets a response with a number of
TXT RRs with a
On Tue, Aug 28, 2018 at 12:34:13PM +0200,
Willem Toorop via Unbound-users wrote
a message of 17 lines which said:
> [willem@bela ~]$ dig @localhost trustanchor.unbound. TXT CH +short
> ". 19036 20326"
> "2018-08-12.automated-ksk-test.research.icann.org. 3934"
Thanks, but it seems to work
I'm compiling a list of commands to check the trust anchors of a
resolver (for the Day of Doom 11 october) like 'rndc managed-keys
status' for BIND.
With Unbound, the only solution I find is to cat the trust anchor
file, which is less convenient, since its location is
system-dependent.
Any way
