DNS AdBlocker Verification #2887

New issue

Closed

opened 2026-02-28 03:10:29 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-28 03:10:29 -05:00

Owner

Originally created by @madereddy on GitHub (Dec 6, 2023).

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

I checked and didn't find similar feature request

🏷️ Feature Request Type

Other

🔖 Feature description

I have NextDNS setup currently and during router updates the configuration gets lost. I was configuring UptimeKuma to alert me if the configuration changes, but when checking a known ad URL with DNS monitor, it resolves back to 0.0.0.0 which means it successfully resolves.

I would like a way to mark 0.0.0.0 DNS resolutions as failures.

✔️ Solution

Check box to resolve 0.0.0.0 as a failure.

❓ Alternatives

Tried using other monitors, but the default DNS resolver in uptime does not use the routers DNS.

📝 Additional Context

No response

Originally created by @madereddy on GitHub (Dec 6, 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 Other ### 🔖 Feature description I have NextDNS setup currently and during router updates the configuration gets lost. I was configuring UptimeKuma to alert me if the configuration changes, but when checking a known ad URL with DNS monitor, it resolves back to 0.0.0.0 which means it successfully resolves. I would like a way to mark 0.0.0.0 DNS resolutions as failures. ### ✔️ Solution Check box to resolve 0.0.0.0 as a failure. ### ❓ Alternatives Tried using other monitors, but the default DNS resolver in uptime does not use the routers DNS. ### 📝 Additional Context _No response_

deekerman

2026-02-28 03:10:29 -05:00

closed this issue
added the
feature-request

A:monitor
labels

deekerman commented

2026-02-28 03:10:36 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Dec 6, 2023):

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 commented on GitHub (Dec 6, 2023): 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