Blacklist reaction speed #2249
Unanswered
sergeevabc
asked this question in
Q&A
Replies: 1 comment 4 replies
-
Here are the differences: No. Time Source Destination Protocol Length Info
28 1.816854 127.0.0.1 127.0.0.1 DNS 60 Standard query 0x1879 A zykumw.com
29 1.817132 127.0.0.1 127.0.0.1 DNS 126 Standard query response 0x1879 A zykumw.com HINFO This query has been locally blocked by dnscrypt-proxy
65 3.958121 127.0.0.1 127.0.0.1 DNS 64 Standard query 0xd572 A ads.google.com
66 3.958240 127.0.0.1 127.0.0.1 DNS 80 Standard query response 0xd572 A ads.google.com A 0.0.0.0
22 1.672133 127.0.0.1 127.0.0.1 DNS 59 Standard query 0x85fa A 003999.cc
23 1.672317 127.0.0.1 127.0.0.1 DNS 59 Standard query response 0x85fa A 003999.cc It returns a That seems neither to be recognized by |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Dear @jedisct1,
even with a relatively small blacklist (~1 MB) loaded in DNSCrypt 2.1.2 on Windows 7 x64,
I wait for a couple of seconds after executing
ping someBlockedAddress.tld
(e.g.zykumw.com
)before it reports
Ping request could not find host zykumw.com
,whereas I expect it to report instantly.
No logging and other lists (e.g.
%systemroot%\system32\drivers\etc\hosts
) are used.Why the delay?
Maybe something should be tuned in
dnscrypt-proxy.toml
?Or
ping
is not a reliable way to measure the blacklist reaction speed?Beta Was this translation helpful? Give feedback.
All reactions