v1.2.8#50
Merged
Merged
Conversation
Replaced fetch()-based checkDnsbl with proper DNS resolution via dns.promises.Resolver (1.1.1.1, 8.8.8.8) to avoid false positives caused by ISP DNS hijacking (e.g. Free).
- Log which blacklists match when an IP is flagged - Add 3s timeout to DNS resolver
express.json() and express.urlencoded() were after advancedBotProtection, causing req.body to be undefined and triggering honeypot check errors.
- Revert from hardcoded Cloudflare/Google DNS resolvers to system DNS - Match only 127.0.0.x (standard DNSBL listing codes), excluding non-standard codes like 127.255.255.254 (Spamhaus query refusal caused by ISP DNS issues like Free's)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.