You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
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.
The text was updated successfully, but these errors were encountered: