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

[FR] make option to mitigate DNS cache poision attack by switching to TCP resolve for attacked domain #1003

Open
rozhuk-im opened this issue Jan 31, 2024 · 0 comments

Comments

@rozhuk-im
Copy link

Current behavior
There is no auto mitigation for attacked domain in case DNSEec is off.
unwanted-reply-threshold only can flush caches - it is bad in all cases.

Describe the desired feature
unbound can detect non queried answers and mark domains from answers as attacked in cache.
Then renew time is come unbound can check "attacked" flag and if it set - send queries via TCP first.
Also some rate limit and expire time for this flag should exist to not thread every non queried answer as attack.
Attack flag should expire after some time.
It is some extension for unwanted-reply-threshold option.

Potential use-case
In case DNSSec is off there is only few options to mitigate unwanted-reply~s cache poisoning like use-caps-for-id.

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

No branches or pull requests

1 participant