uptime-kuma icon indicating copy to clipboard operation
uptime-kuma copied to clipboard

DNS Overwrite/Assignment for URL in Monitoring

Open Lakr233 opened this issue 2 years ago • 3 comments

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

  • [X] I checked and didn't find similar feature request

🏷️ Feature Request Type

Other

🔖 Feature description

I have a domain (let's say www.example.com) redirected to a local host device (let's say 10.10.10.15) on my router so I can access my service quickly when I connect to my local network, but I may want to check it's public ip (let's say 123.123.123.123) for service availability matters, I've got jump/reversed proxy for that port mapping it to public.

✔️ Solution

I'd like to have an option for overwrite server ip address without changing the dns server it self.

截屏2022-03-28 00 10 58

❓ Alternatives

No response

📝 Additional Context

No response

Lakr233 avatar Mar 27 '22 16:03 Lakr233

👍🏻 for this feature!

gaby avatar Mar 28 '22 04:03 gaby

This would be a great feature to add to the project!

Great tool overall!

dkay-zaxxx avatar Mar 30 '22 07:03 dkay-zaxxx

I am also looking for a similar option.

I know it's possible to do a similar 'outside check' through a proxy. But finding a free proxy to do that check is annoying and they never live long enough to make it useful through uptime-kuma.

The possibility to bypass the docker DNS, would make it easier to be able to check local DNS and remote DNS for a service.

UbioZur avatar Jul 28 '22 10:07 UbioZur

I'm also looking for this feature! I want to customize the DNS for each HTTP type of monitor to differentiate between internal and external networks.

miHaMu avatar Nov 27 '23 10:11 miHaMu

@Lakr233

You can do that 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

I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/2991 https://github.com/louislam/uptime-kuma/issues/3979 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?) ^^

Note that our contribution guide can be found here and that we are open to contributions if you adhere to this

CommanderStorm avatar Nov 27 '23 16:11 CommanderStorm

@CommanderStorm Thank you for providing this level of detail, and I have confirmed that it is working as expected.

Lakr233 avatar Nov 28 '23 05:11 Lakr233