DNS Check with support for searching for (a part) value.

[josefglatz]

⚠️ 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 DNS check is great! However it would be a real benefit if it is also possible to search (nonregex oder regex) for patterns in e.g. all or a specific TXT entry.

For example: Check SPF Record if the string "include:foobar.com" is included.

✔️ Solution

In my use-case this is something the HTTP(s) Checks also supports with Content.

❓ Alternatives

None found

📝 Additional Context

[salixh5]

Not just TXT entry, this would be useful for pretty much every type of DNS entry. For example I want to monitor if A entry still points to a certain server or NS are still the same.

[ndizazzo]

For example I want to monitor if A entry still points to a certain server or NS are still the same.

Or the inverse (support upside-down mode), I want to see if my PiHole is returning anything except 0.0.0.0 for a specific domain to test if the FTL service has crashed or the AdList was modified.

[vodium-vastro]

I agree with @jeifour, being able to verify that a record equals something you expect and alerts you if it has been changed would be VERY valuable.

Thanks for all the hard work

[it2serve]

Not just TXT entry, this would be useful for pretty much every type of DNS entry. For example I want to monitor if A entry still points to a certain server or NS are still the same.

I'm also looking for a monitor like this. If the IP adress of a DNS record is different from what we expect, an alert is needed.

[mgrn0]

@josefglatz this is an extremely good proposal, would be really useful to see something like that supported.

[CommanderStorm]

@thcnunz Please refrain from posting +1 / requests for updates things on issues, as this makes issue-management harder. Issues are for discussing what needs to be done how by whom. We use 👍🏻 on issues to prioritise work.

[CommanderStorm]

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