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

Save Resolved DNS IP #1924

Open
1 task done
dritz-ecloud opened this issue Jul 19, 2022 · 2 comments
Open
1 task done

Save Resolved DNS IP #1924

dritz-ecloud opened this issue Jul 19, 2022 · 2 comments
Labels
area:monitor Everything related to monitors feature-request Request for new features to be added type:enhance-existing feature wants to enhance existing monitor

Comments

@dritz-ecloud
Copy link

dritz-ecloud commented Jul 19, 2022

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

  • I checked and didn't find similar feature request

🏷️ Feature Request Type

New Monitor

🔖 Feature description

Record the resolved IP address of the instance targeted for the health check.

✔️ Solution

Ideally we would like Uptime Kuma to record the resolved DNS entry at the time of the request. This would be something like the results of dig www.example.com A performed immediately preceding the HTTP(S) health check. Alternatively this could use the IP of the instance responding to the health check.

This check would ensure that DNS is not pointing to a stale/invalid record as a cause of the failed check.

❓ Alternatives

We use a separate service for DNS propagation checks, as well as querying name servers using dig.

📝 Additional Context

Similar feature offered by another service: https://support.uptime.com/hc/en-us/articles/360001366189-DNS-Server-Check-Basics

@dritz-ecloud dritz-ecloud added the feature-request Request for new features to be added label Jul 19, 2022
@CommanderStorm
Copy link
Collaborator

@dritz-ecloud
I think this is a duplicate of #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?) ^^

@septemberservices
Copy link

I read this request as a different request. In my opinion it's worded a bit strangely, but what I think it's about is logging the actual IP address that was connected to.

For our use case: we have a monitor that sometimes complains about a wrong certificate. This certificate is for a completely different server (that is being monitored). If the monitoring message would show what IP address was connected to in order to retrieve the bad certificate, that would help us locate the problem.

@CommanderStorm CommanderStorm added area:monitor Everything related to monitors type:enhance-existing feature wants to enhance existing monitor labels Dec 4, 2023
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 feature-request Request for new features to be added type:enhance-existing feature wants to enhance existing monitor
Projects
None yet
Development

No branches or pull requests

3 participants