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 option for expected results from a DNS query. #4896

Closed
di-org opened this issue Jun 29, 2024 · 1 comment
Closed

Add option for expected results from a DNS query. #4896

di-org opened this issue Jun 29, 2024 · 1 comment
Labels
area:monitor Everything related to monitors duplicate This issue or pull request already exists feature-request Request for new features to be added

Comments

@di-org
Copy link

di-org commented Jun 29, 2024

πŸ“‘ I have found these related issues/pull requests

N/A

🏷️ Feature Request Type

Change to existing monitor

πŸ”– Feature description

If someone were to perform a query such as "dig domain.com txt", there could be one to many results. The current mechanism for this checks just verifies that there is a return, but does not have the ability to monitor of an expected result. For example, if I wanted to make sure my SPF record hasn't changed, I could monitor for:

"v=spf1 include:mailserver.com ~all"

If that result doesn't match (e.g. changed, deleted), then it would alert.

βœ”οΈ Solution

Include a field / option to monitor for an expected result, similar as to the "HTTP(s) - Keyword".

As well, this should not just apply to TXT records. It would be equally important for A, AAAA, MX, SOA, etc.

❓ Alternatives

N/A

πŸ“ Additional Context

N/A

@di-org di-org added the feature-request Request for new features to be added label Jun 29, 2024
@CommanderStorm CommanderStorm added duplicate This issue or pull request already exists area:monitor Everything related to monitors labels Jun 29, 2024
@CommanderStorm
Copy link
Collaborator

Checking the content of dns queries is tracked in #432 and the PR to resolve this will be #3919, but it will be a while before it gets implemented.

=> closing as a duplicate

@CommanderStorm CommanderStorm closed this as not planned Won't fix, can't repro, duplicate, stale Jun 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:monitor Everything related to monitors duplicate This issue or pull request already exists feature-request Request for new features to be added
Projects
None yet
Development

No branches or pull requests

2 participants