From 9d24bd7cc11653ac4bb3cb3df29f02fc191f8c46 Mon Sep 17 00:00:00 2001
From: Frank Denis <124872+jedisct1@users.noreply.github.com>
Date: Mon, 26 Feb 2024 16:03:16 +0100
Subject: [PATCH] Updated Load Balancing Options (markdown)

---
 Load-Balancing-Options.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/Load-Balancing-Options.md b/Load-Balancing-Options.md
index 368128a..f773ca0 100644
--- a/Load-Balancing-Options.md
+++ b/Load-Balancing-Options.md
@@ -10,7 +10,9 @@ When `dnscrypt-proxy`:
 * Each time the server certificates (for DNSCrypt servers) are retrieved/validated (every `cert_refresh_delay` minutes, 60 minutes minimum)
 * Each time the list of servers is retrieved (every `refresh_delay` hours)
 
-It calculates an initial RTT (Round-Trip Time) estimation for each resolver (for DoH servers, two initial test queries are made). This list is then sorted from fastest to slowest resolver.
+It calculates an initial RTT (Round-Trip Time) estimation for each resolver (for DoH servers, two initial test queries are made to measure latency with a reused connection). For DoH/ODoH/DoOH servers, the latency is computed by sending a query for the name servers of the root zone, which is always cached by resolvers. For DNSCrypt/Anonymized DNSCrypt, the latency is measured when retrieving the certificates (which also doesn't need the resolver to wait for upstream servers).
+
+The list is then sorted from fastest to slowest resolver.
 
 ## How the servers are sorted