Add a new Domain/Subdomain-Type "DynDNS", which redirects to a dynamic IP-Address like dyndns.org and similar sites including an api to sync the current ip address through url call.
Thank you for your input. We will definitely look into integrating DynDNS in our future releases
2 years later ..... no dyndns support ... :-(
A dyndns Service would be fine.
Has there been any progress on this? Many server providers also provide monitoring services, but if we choose to limit ICMP to whitelist, then these monitoring services fail because they need a range of IPs AND hostnames whitelisted.
Sven P. commented
Any update? Would be great to have that Feature!
I would also like to see this certainly easy-to-implement function in Plesk, which would be a dream.
This is without Token but rather easy to integrate i would say, a plugin with usermanagement would be neat..... don't forget ipv6.
What happened to this feature?
Yes would be awesome to update a subdomain with dynamic ip via router (fritzbox) or Tools like directupdate
Would be great if that could be implemented. I always use the Plesk Firewall to deny access to ssh, but because of my dynamic IP I have to change the IP a few times a year.
Miguel Antequera commented
Possibility of including hostnames in firewall rules, such no-ip or dyndns addresses.
If wildcards permitted (for example *.amazon.cn) FANTASTIC !!!
Juergen Trapp commented
Would be awesome
NoIP is dead because TakeDown from Microsoft.... Now we need this Feature....
Patrick Schwarz commented
This is a very important function and should be integrated into plesk. Since some months, some of the Dyndns-providers closed their free dyndns services. You need them e.g. for connecting to home VPNs to manage the router, home automation systems, telephone systems, local servers and get access to local files e.g.
There is already a plugin
Would be nice if Plesk will integrate such an important function by themselves ..
The idea here would be to have a type "DynDNS"
DNS server allows to set a different TTL for these entries, allowing changes to be rolled out much quicker to other servers
The way it should work:
call an API, which is secured with HTTP Auth
where you allow updating this entry with a new IP address
I've just found a proper document which describes how this should work
DynDNS API document:
If you drop me an email ill tell you how I work around this at the moment and what solution we would expect
Sergey Ugdyzhekov commented
Could you explain your workflow with more details?