allow more than one resolver server for dns checks #4203

New issue

Closed

opened 2026-02-28 03:54:36 -05:00 by deekerman · 2 comments

deekerman commented

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

Owner

Originally created by @Waldorf3 on GitHub (Jul 14, 2025).

I have not

🏷️ Feature Request Type

Change to existing monitor

🔖 Feature description

Today Cloudflare 1.1.1.1 went down. and I had to spend half an hour trouble shooting until I realized the problem was elsewhere. I tried adding multiple resolver servers but while there is apparenly no control of what is entered, multiple resolver servers whether separated by space or comma throws errors.

✔️ Solution

Suggest allowing multiple resolver servers to avoid this false positive.

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @Waldorf3 on GitHub (Jul 14, 2025). ### 📑 I have found these related issues/pull requests I have not ### 🏷️ Feature Request Type Change to existing monitor ### 🔖 Feature description [Today Cloudflare 1.1.1.1 went down.](https://www.reddit.com/r/CloudFlare/comments/1m004ua/1111_is_down_it_seems/) and I had to spend half an hour trouble shooting until I realized the problem was elsewhere. I tried adding multiple resolver servers but while there is apparenly no control of what is entered, multiple resolver servers whether separated by space or comma throws errors. ### ✔️ Solution Suggest allowing multiple resolver servers to avoid this false positive. ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

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

closed this issue
added the
feature-request

A:monitor

type:enhance-existing
labels

deekerman commented

2026-02-28 03:54:42 -05:00

Author

Owner

@raabmar commented on GitHub (Jul 15, 2025):

I had the same issue, I thought the entire internet went down at first. It was not only 1.1.1.1 but also 8.8.8.8 that was affected I think.

I am glad I read it was not only me impacted by it. I tried to search to pinpoint it and I think in my case I have the dns resolver added in the docker run command.

It seems to me there are different levels in were DNS resolver could be defined, but not sure about the details here

@raabmar commented on GitHub (Jul 15, 2025): I had the same issue, I thought the entire internet went down at first. It was not only 1.1.1.1 but also 8.8.8.8 that was affected I think. I am glad I read it was not only me impacted by it. I tried to search to pinpoint it and I think in my case I have the dns resolver added in the docker run command. It seems to me there are different levels in were DNS resolver could be defined, but not sure about the details here

deekerman commented

2026-02-28 03:54:42 -05:00

Author

Owner

@Waldorf3 commented on GitHub (Jul 15, 2025):

Once I realized the problem was 1.1.1.1 I changed to 1.0.0.1 and after that it worked. I would still like to have more than one resolver, just like you have most everywhere else.

@Waldorf3 commented on GitHub (Jul 15, 2025): Once I realized the problem was 1.1.1.1 I changed to 1.0.0.1 and after that it worked. I would still like to have more than one resolver, just like you have most everywhere else.