Save Resolved DNS IP - Githubissues

dritz-ecloud commented 2 years ago

⚠️ 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

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

CommanderStorm commented 1 year ago

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

septemberservices commented 1 year ago

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.

louislam / uptime-kuma

Save Resolved DNS IP #1924