📑 I have found these related issues/pull requests

Description:

When monitoring a Steam game server with Kuma, I’m encountering an issue where using a domain name as the host doesn’t work properly. This is because Steam’s API uses the server’s public IP address, not the domain name, for health checks.

My context:

I have a dynamic IP, so I use a domain name (via dynamic DNS) to always point to my current IP.

When I enter the domain name in Kuma, the health check fails because Steam tries to use the domain name, not the resolved IP.

Expected behavior:

I would expect Kuma to resolve the domain name to its current IP and use that IP in the request.

🏷️ Feature Request Type

Other

🔖 Feature description

Please consider adding a feature that allows Kuma to resolve a domain name to its IP address and then use that IP when performing Steam server health checks.

Why this is useful:

Steam’s API works only with IPs, not domain names.

For users with dynamic IPs, using a static domain name is necessary.

This feature would make Kuma compatible with dynamic IP setups while still enabling Steam server monitoring.

✔️ Solution

Suggestion:

A checkbox or option like “Resolve domain to IP before request” could be added for relevant monitor types.

❓ Alternatives

No response

📝 Additional Context

No response