DNS keyword check #2225

Closed
opened 2026-02-28 02:47:13 -05:00 by deekerman · 4 comments
Owner

Originally created by @5UFKEFU on GitHub (Jun 2, 2023).

⚠️ Please verify that this feature request has NOT been suggested before.

  • I checked and didn't find similar feature request

🏷️ 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

Originally created by @5UFKEFU on GitHub (Jun 2, 2023). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ 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_
deekerman 2026-02-28 02:47:13 -05:00
Author
Owner

@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

@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
Author
Owner

@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.

@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.
Author
Owner

@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 (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?) ^^
Author
Owner

@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.

@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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#2225
No description provided.