Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add OpenBLD.net #918

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Add OpenBLD.net #918

wants to merge 4 commits into from

Conversation

m0zgen
Copy link

@m0zgen m0zgen commented Jun 2, 2024

Hello,

Add please to this project OpenBLD.net service with suspicious domains blocking functionality.

Thank you!

Hello,

Add please to this project OpenBLD.net service with suspicious domains blocking functionality.

Thank you!
v3/public-resolvers.md Outdated Show resolved Hide resolved
v3/public-resolvers.md Outdated Show resolved Hide resolved
@demarcush
Copy link
Contributor

Beside the with with typo, all looks good.
@jedisct1

m0zgen added 2 commits July 27, 2024 18:58
Will add later, after will sure that deploy test will successes.
@jedisct1
Copy link
Member

jedisct1 commented Aug 3, 2024

Has 24h/48h logs for DDoS/Flood attack mitigation

I'm not sure that this qualifies as nolog. Storing logs for so long should never be necessary for flood mitigation.

@demarcush
Copy link
Contributor

I believe this repo's README should specifically outline what all the options mean.

@m0zgen
Copy link
Author

m0zgen commented Aug 5, 2024

Hello, I reviewed prcheck new entries failed step in Actions page, this fails has nothing to do with my servers. What needs to be done to fix this error? Help please.

@jedisct1 here there is not only protection from DDoS attacks, sometimes it is necessary for detecting DNS tunneling or interval requests that bots generate, if necessary I can reset the timing to 24 hours, this is the minimum necessary time lag for objective detection.

@m0zgen
Copy link
Author

m0zgen commented Nov 18, 2024

Hey guys, maybe does it make sense to create a new PR with a actual branch or how can this merge conflict be resolved?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants