louislam/uptime-kuma

Dyndns based Steam game server monitoring

Open

#5934 opened on Jun 18, 2025

View on GitHub
 (9 comments) (1 reaction) (0 assignees)JavaScript (86,760 stars) (7,844 forks)batch import
A:monitorfeature-requestgood first issue

Description

📑 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

Contributor guide

Tech stack
javascriptnodejsvue
Domain
backenddevopsapi
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Examine existing Steam monitor type implementation in uptime kuma (likely in `server/monitor types/steam.js` or similar). Add a configuration option to resolve the domain name to an IP before making the API request. The implementation should modify the monitor's `check` function to optionally use `dns.resolve` to convert the hostname to an IP address. Ensure backward compatibility and add UI elements (checkbox) in the frontend component for Steam monitors. Review comment history for any additional maintainer guidance.