Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: DynDNS service #619

Open
Zetanova opened this issue Feb 7, 2025 · 3 comments
Open

Feature: DynDNS service #619

Zetanova opened this issue Feb 7, 2025 · 3 comments

Comments

@Zetanova
Copy link

Zetanova commented Feb 7, 2025

I would have an maybe good idea for probe providers

In the probe settings the user could set a setting to allow dynDNS service
and globalping could create DNS records under example:
probe-name.account-name.dyn.globalping.io

It would relatively simple to implement over powerdns or coredns.

@MartinKolarik
Copy link
Member

What would be the use case for those DNS records? Our probes are not expected to receive any direct requests.

@Zetanova
Copy link
Author

Zetanova commented Feb 9, 2025

Globalping would provide dyndns service for the probe operator.

it is basically a well known record that the operator could use as an CNAME
example: myhome.mydomain.com CNAME probe-name.account-name.dyn.globalping.io

The probe itself receives no external requests.
It would make services like dd-wrt / openwrt: https://github.com/troglobit/inadyn redundant.

@jimaek
Copy link
Member

jimaek commented Feb 10, 2025

While it could be a cool feature I am more worried about abuse. This would mean that people could then host websites under "probe-name.account-name.dyn.globalping.io" including phishing and illegal content. That adds an extra layer of complexity to handle.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants