From 24bf267e055d33f53520b64820ebf3601525c6fa Mon Sep 17 00:00:00 2001 From: Alexandre Dulaunoy Date: Thu, 9 May 2024 11:31:20 +0200 Subject: [PATCH] chg: [pdns] answers might be empty, inconsistent and different across different Passive DNS --- i-d/pdns-qof.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i-d/pdns-qof.xml b/i-d/pdns-qof.xml index 3328f86..ed9e80f 100644 --- a/i-d/pdns-qof.xml +++ b/i-d/pdns-qof.xml @@ -172,7 +172,7 @@ The document does not describe the protocol (e.g. WHOIS As Passive DNS servers can include protection mechanisms for their operation, results might be different due to those protection measures. These mechanisms filter out DNS answers if they fail some criteria. The bailiwick algorithm protects the Passive DNS Database from cache poisoning attacks. - Another limitation that clients querying the database need to be aware of is that each query simply gets a snapshot-in-time answer at the time of querying. Clients MUST NOT rely on consistent [what does "consistent" mean in this context? Coherent?] answers. Nor should they assume that answers will be identical across multiple Passive DNS Servers. + Another limitation that clients querying the database need to be aware of is that each query simply gets a snapshot-in-time answer at the time of querying. Clients MUST NOT rely on existing answers from different Passive DNS database. Nor should they assume that answers will be identical across multiple Passive DNS Servers.