Is 'Blocked IPs' functionality broken (DNS rebinding tests resolve) #2896
Closed
cobratbq
started this conversation in
Potential issues
Replies: 2 comments
-
This might have been fixed in commit 94323d5, though that commit is not part of release If this is indeed the fix, then it might be good to add a note to release 2.1.12 to warn of broken functionality. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I think that was fixed in 94323d5 |
Beta Was this translation helpful? Give feedback.
0 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.
-
Is the Blocked IPs functionality broken? It seems like the DNS rebinding protection ip-blocks successfully resolve. (I.e. they shouldn't.)
dnscrypt-proxy.toml
(dnscrypt-proxy 2.1.12, from github, today)blocked-ips.txt
systemctl status dnscrypt-proxy
host -v net10.rebindtest.com.
dnscrypt-proxy -config /etc/dnscrypt-proxy/dnscrypt-proxy.toml -resolve net10.rebindtest.com.
Blocked IP entries are absent from blocked-ips log-file.
Just did a quick check: it works as expected on version
2.1.8
. (I used the2.1.12
config but with keyhttp3_probe
and sectionmonitoring_ui
disabled.)P.s.: I recently fixed your
127/8
IP-range from127.0.0.*
to127.*
on the wiki.Beta Was this translation helpful? Give feedback.
All reactions