Update DNSSEC validation deployment stats in DNSSEC Guide

diff --git a/doc/dnssec-guide/getting-started.rst b/doc/dnssec-guide/getting-started.rst
index 60a3c2d79805213acca3c8b8708bbdb243f520a2..458a2eb2a60a202c274aa26e2f77de373e53f69a 100644 (file)
--- a/doc/dnssec-guide/getting-started.rst
+++ b/doc/dnssec-guide/getting-started.rst
@@ -85,18 +85,13 @@ enhancements for an authoritative server with signed zones:
    you have some truly outdated hardware.
 
 One factor to consider, but over which you really have no control, is
-the number of users who query your domain name who themselves have DNSSEC enabled. It was
-estimated in late 2014 that roughly 10% to 15% of the Internet DNS
-queries were DNSSEC-aware. Estimates by `APNIC <https://www.apnic.net/>`__
-suggest that in 2020 about `one-third <https://stats.labs.apnic.net/dnssec>`__ of all queries are
-validating queries, although the percentage varies widely on a
-per-country basis. This means that more DNS queries for your domain will
+the number of users who query your domain name who themselves have DNSSEC
+enabled. As of mid-2022, measurements by `APNIC
+<https://stats.labs.apnic.net/dnssec>`__ show 41% of Internet users send
+DNSSEC-aware queries. This means that more DNS queries for your domain will
 take advantage of the additional security features, which will result in
 increased system load and possibly network traffic.
 
-.. [#]
-   https://rick.eng.br/dnssecstat
-
 .. _network_requirements:
 
 Network Requirements