starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

Status from local side via local DNS & CNAME at TCP port #2890

New issue

Closed

opened 2026-02-28 03:10:37 -05:00 by deekerman · 6 comments

deekerman commented

2026-02-28 03:10:37 -05:00

Owner

Originally created by @XHyperDEVX on GitHub (Dec 7, 2023).

⚠️ Please verify that this bug has NOT been raised before.

I checked and didn't find similar issue

🛡️ Security Policy

I agree to have read this project Security Policy

📝 Describe your problem

I have two questions:

I have a local DNS server that forwards "home.local" to a local ip. i want to monitor the access from "home.local". Unfortunately, uptime-kuma can't connect to this local url because it uses external DNS servers, in my case Cloudflare [1.1.1.1].
How can I tell it to query the url at the local DNS server ONLY FOR THIS ONE CONNECTION?

And my second question:

Can I somehow specify a CNAME in the TCP port option? I would like to monitor the HTTP access from outside, i.e. whether one comes into my network from outside via port 80. As I unfortunately do not have a static IP, I have set up a DynDNS service. Unfortunately, I can only enter IPs for the TCP port, not a CNAME. Is there any way to do this?

📝 Error Message(s) or Log

🐻 Uptime-Kuma Version

1.23.7

💻 Operating System and Arch

Debian 12 [..as host system, i use the Uptime-Kuma Docker Image]

🌐 Browser

Edge

🐋 Docker Version

20.10.24

🟩 NodeJS Version

i dont know

Originally created by @XHyperDEVX on GitHub (Dec 7, 2023). ### ⚠️ Please verify that this bug has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### 📝 Describe your problem I have two questions: I have a local DNS server that forwards "home.local" to a local ip. i want to monitor the access from "home.local". Unfortunately, uptime-kuma can't connect to this local url because it uses external DNS servers, in my case Cloudflare [1.1.1.1]. How can I tell it to query the url at the local DNS server ONLY FOR THIS ONE CONNECTION? And my second question: Can I somehow specify a CNAME in the TCP port option? I would like to monitor the HTTP access from outside, i.e. whether one comes into my network from outside via port 80. As I unfortunately do not have a static IP, I have set up a DynDNS service. Unfortunately, I can only enter IPs for the TCP port, not a CNAME. Is there any way to do this? ### 📝 Error Message(s) or Log - ### 🐻 Uptime-Kuma Version 1.23.7 ### 💻 Operating System and Arch Debian 12 [..as host system, i use the Uptime-Kuma Docker Image] ### 🌐 Browser Edge ### 🐋 Docker Version 20.10.24 ### 🟩 NodeJS Version i dont know

deekerman

2026-02-28 03:10:37 -05:00

closed this issue
added the
A:monitor

help

blocked-upstream
labels

deekerman commented

2026-02-28 03:10:44 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Dec 7, 2023):

How can I tell it to query the url at the local DNS server ONLY FOR THIS ONE CONNECTION?

Setting the dns server or response per monitor is currently not configurable.
I am not aware of such a feature request existing (there are different fields => filling out this form is benefitial) ^^

You may be able to get around this with the tools currently at your disposal:

you enter the ip into the url field
you enter the Host header as described in https://github.com/louislam/uptime-kuma/issues/2991

@CommanderStorm commented on GitHub (Dec 7, 2023): > How can I tell it to query the url at the local DNS server ONLY FOR THIS ONE CONNECTION? Setting the dns server or response per monitor is currently not configurable. I am not aware of such a [feature request existing (there are different fields => filling out this form is benefitial)](https://github.com/louislam/uptime-kuma/issues/new?assignees=&labels=feature-request&projects=&template=feature_request.yaml) ^^ You may be able to get around this with the tools currently at your disposal: - you enter the ip into the url field - you enter the [`Host` header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Host) as described in https://github.com/louislam/uptime-kuma/issues/2991

deekerman commented

2026-02-28 03:10:44 -05:00

Author

Owner

@XHyperDEVX commented on GitHub (Dec 7, 2023):

@CommanderStorm
Thank you, that works! I don't know exactly why, but it works! xD

Now I only have the CNAME problem. Do you have a solution for that too?

@XHyperDEVX commented on GitHub (Dec 7, 2023): @CommanderStorm Thank you, that works! I don't know exactly why, but it works! xD Now I only have the CNAME problem. Do you have a solution for that too?

deekerman commented

2026-02-28 03:10:44 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Dec 7, 2023):

github.com/louislam/uptime-kuma@ad4629cb03/server/model/monitor.js (L616)

Calls
github.com/louislam/uptime-kuma@ad4629cb03/server/util-server.js (L103-L107)

and https://www.npmjs.com/package/tcp-ping does not have this functionality.
Please add this feature request here: https://github.com/apaszke/tcp-ping/issues

@CommanderStorm commented on GitHub (Dec 7, 2023): https://github.com/louislam/uptime-kuma/blob/ad4629cb038c5b47fb04053f48c6fa905644e386/server/model/monitor.js#L616 Calls https://github.com/louislam/uptime-kuma/blob/ad4629cb038c5b47fb04053f48c6fa905644e386/server/util-server.js#L103-L107 and https://www.npmjs.com/package/tcp-ping does not have this functionality. Please add this feature request here: https://github.com/apaszke/tcp-ping/issues

deekerman commented

2026-02-28 03:10:44 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Dec 7, 2023):

Note that if you need dns resolution, you are likely monitoring a website => the https monitor is be better suited for this.

@CommanderStorm commented on GitHub (Dec 7, 2023): Note that if you need dns resolution, you are likely monitoring a website => the https monitor is be better suited for this.

deekerman commented

2026-02-28 03:10:44 -05:00

Author

Owner

@XHyperDEVX commented on GitHub (Dec 7, 2023):

Thanks

@XHyperDEVX commented on GitHub (Dec 7, 2023): Thanks

deekerman commented

2026-02-28 03:10:44 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Dec 7, 2023):

Another note: per monitor dns is tracked in #1302 and the discussion for implementing this is in #2055

@CommanderStorm commented on GitHub (Dec 7, 2023): Another note: per monitor dns is tracked in #1302 and the discussion for implementing this is in #2055