mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
DNS keyword check #2225
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#2225
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @5UFKEFU on GitHub (Jun 2, 2023).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
New Monitor
🔖 Feature description
The current DNS detection only detects if there is a resolution result, but this is not practical, and in practice DNS pollution is more important to detect.
✔️ Solution
Add the keyword check of DNS.
❓ Alternatives
No response
📝 Additional Context
No response
@CommanderStorm commented on GitHub (Jun 2, 2023):
If you are using a normal, reputable DNS vendor (supporting DNSSEC), this attack vector is basically negligible from what I have read
⇒ I don't see how this monitor type would be an advantage.
Please go into more detail
@5UFKEFU commented on GitHub (Jun 2, 2023):
If you live in China, you will feel that very important, China has an Internet firewall, specifically to pollute this, so it is necessary to say.
@CommanderStorm commented on GitHub (Jul 26, 2023):
I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/432
If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage?
If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^
@CommanderStorm commented on GitHub (Dec 3, 2023):
@5UFKEFU
We are consolidating duplicate issues a bit to make issue management easier.
I think, we should track this issue in #432 as there is no functional difference (maybe just small naming differences, but nothing that would require a different issue imo)
⇒ I am going to close this as a duplicate.