adulau/pdns-qof
1
0
Fork 0
mirror of https://github.com/adulau/pdns-qof.git synced 2024-05-20 10:52:10 +00:00
Code Issues Packages Projects Releases Wiki Activity

chg: [pdns] answers might be empty, inconsistent and different across different Passive DNS

Browse source
This commit is contained in:
Alexandre Dulaunoy 2024-05-09 11:31:20 +02:00
parent 0e7b9f2f52
commit 24bf267e05
Signed by: adulau
GPG key ID: 09E2CD4944E6CBCD
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
i-d/pdns-qof.xml
View file

@ -172,7 +172,7 @@ The document does not describe the protocol (e.g. <xref target="RFC3912">WHOIS</
<section title="Limitation">
<t> 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 <xref target="BAILIWICK">bailiwick algorithm</xref> protects the Passive DNS Database from <xref target="CACHEPOISONING">cache poisoning attacks</xref>.
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.
</t>
</section>
<section title="Common Output Format">