From 15eea792b9289c38dd9efd4bd5919e55a6ad0e08 Mon Sep 17 00:00:00 2001 From: Suzanne Goldlust Date: Wed, 29 Nov 2023 22:44:17 +0000 Subject: [PATCH] Fix broken link to TLD DNSSEC stats --- doc/dnssec-guide/validation.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/dnssec-guide/validation.rst b/doc/dnssec-guide/validation.rst index a499587983..33958bb2a0 100644 --- a/doc/dnssec-guide/validation.rst +++ b/doc/dnssec-guide/validation.rst @@ -706,7 +706,7 @@ database (``managed-keys.bind.jnl``) as the source of key information. Explicit management of keys was common in the early days of DNSSEC, when neither the root zone nor many top-level domains were signed. Since -then, `over 90% `__ of +then, `over 90% `__ of the top-level domains have been signed, including all the largest ones. Unless you have a particular need to manage keys yourself, it is best to use the BIND defaults and let the software manage the root key.