starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

Make the DNS check also validate a specific record value #677

New issue

Closed

opened 2026-02-28 01:54:23 -05:00 by deekerman · 6 comments

deekerman commented

2026-02-28 01:54:23 -05:00

Owner

Originally created by @d3xt3r01 on GitHub (Dec 20, 2021).

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

I checked and didn't find similar feature request

🏷️ Feature Request Type

UI Feature

🔖 Feature description

I'd like to be able to validate the dns reply value also, not just that there is an answer

✔️ Solution

I'd like to be able to specify the expected value (optional) for a dns check

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @d3xt3r01 on GitHub (Dec 20, 2021). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type UI Feature ### 🔖 Feature description I'd like to be able to validate the dns reply value also, not just that there is an answer ### ✔️ Solution I'd like to be able to specify the expected value (optional) for a dns check ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

2026-02-28 01:54:23 -05:00

closed this issue
added the
feature-request
label

deekerman commented

2026-02-28 01:54:26 -05:00

Author

Owner

@reitermarkus commented on GitHub (Jan 22, 2022):

Would we very useful for monitoring whether my LanCache is working as intended.

@reitermarkus commented on GitHub (Jan 22, 2022): Would we very useful for monitoring whether my LanCache is working as intended.

deekerman commented

2026-02-28 01:54:26 -05:00

Author

Owner

@m0dd3r43v3r commented on GitHub (Feb 14, 2022):

This would be amazing to monitor unexpected DNS changes by registrar.

@m0dd3r43v3r commented on GitHub (Feb 14, 2022): This would be amazing to monitor unexpected DNS changes by registrar.

deekerman commented

2026-02-28 01:54:26 -05:00

Author

Owner

@tracure1337 commented on GitHub (May 27, 2022):

This would be super useful indeed.

@tracure1337 commented on GitHub (May 27, 2022): This would be super useful indeed.

deekerman commented

2026-02-28 01:54:26 -05:00

Author

Owner

@jemand771 commented on GitHub (Jun 1, 2022):

while the suggested config options are different, this feels similar to #432
also note that another possible solution was/is being discussed in #518

@jemand771 commented on GitHub (Jun 1, 2022): while the suggested config options are different, this feels similar to #432 also note that another possible solution was/is being discussed in #518

deekerman commented

2026-02-28 01:54:26 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Jul 27, 2023):

@d3xt3r01
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?) ^^

(this issue is the less popluar one by numner of 👍🏻 on issues, which some maintainers use to prioritise work)

@CommanderStorm commented on GitHub (Jul 27, 2023): @d3xt3r01 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?) ^^ (this issue is the less popluar one by [numner of 👍🏻 on issues](https://github.com/louislam/uptime-kuma/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc), which some maintainers use to prioritise work)

deekerman commented

2026-02-28 01:54:26 -05:00

Author

Owner

@d3xt3r01 commented on GitHub (Jul 27, 2023):

See #432

@d3xt3r01 commented on GitHub (Jul 27, 2023): See #432