Legacy DDNS retiring without a replacement for URL callbacks?

[joecool]

I am currently on v23.1_6 using the legacy dynamic dns client and updating my domain on porkbun.com.  It doesn't have "normal" DDNS capabilities but does have an API (https://kb.porkbun.com/article/190-getting-started-with-the-porkbun-api).  They have a couple of clients linked there already but I'm using a homemade php script.  To call it, I am sending:

    Update URL: http://10.1.2.12/porkbun_ddns.php?domain=mydomain.com&hosts=*,ipv4&ip=%IP%
    Result Match: I have "SUCCESS" coming back from my update script if it succeeds.

I just noticed the message "Please make sure to upgrade to os-ddclient before 23.7 is released as this plugin will be removed from our repository". I installed the new plugin but it doesn't look like calling a custom URL is supported? Am I missing something and is there a way to support this setup?

If not, is there a way to beg the devs to add Porkbun as an option prior to v23.7's release?  As of right now, if the legacy DDNS client gets turned off, I'm hosed.

TIA!

[HunvHunv]

Hi,
I have the same problem.
Is there any solution? Would be a big problem for me, because I cannot change the provider for several reasons.
In my case in the legacy dynamic dns client I can call for the Update URL:
https://update.twodns.de/update?hostname=myserver.dynvpn.de&ip=%IP%
I don't see that I can do this in the new one.
If I select "custom", I get a "Server" field, but that field only accepts servernames/IPs and not Update URLs. So
1. What is this field for
2. How to call Update URLs in the new DDNS plugin?

[chemlud]

Hi,
I have the same problem.
Is there any solution? Would be a big problem for me, because I cannot change the provider for several reasons.
In my case in the legacy dynamic dns client I can call for the Update URL:
https://update.twodns.de/update?hostname=myserver.dynvpn.de&ip=%IP%
I don't see that I can do this in the new one.
If I select "custom", I get a "Server" field, but that field only accepts servernames/IPs and not Update URLs. So
1. What is this field for
2. How to call Update URLs in the new DDNS plugin?

@1. Try: update.twodns.de
@2. Apparently no way to enter them directly, but the plugin will generate something along the line of your URL.

You don't need user name and password for updating? Really? Then leave these empty. Try DYNDNS2 and if that doesn't work try DYNDNS1 as "Method". Try with TLS, or maybe without.

PS:

According to this here

https://www.twodns.de/en/faqs#faq2

I would enter your email as user name and your password in the plugin...

[HunvHunv]

Hi,
I have the same problem.
Is there any solution? Would be a big problem for me, because I cannot change the provider for several reasons.
In my case in the legacy dynamic dns client I can call for the Update URL:
https://update.twodns.de/update?hostname=myserver.dynvpn.de&ip=%IP%
I don't see that I can do this in the new one.
If I select "custom", I get a "Server" field, but that field only accepts servernames/IPs and not Update URLs. So
1. What is this field for
2. How to call Update URLs in the new DDNS plugin?

@1. Try: update.twodns.de
@2. Apparently no way to enter them directly, but the plugin will generate something along the line of your URL.

You don't need user name and password for updating? Really? Then leave these empty. Try DYNDNS2 and if that doesn't work try DYNDNS1 as "Method". Try with TLS, or maybe without.

PS:

According to this here

https://www.twodns.de/en/faqs#faq2

I would enter your email as user name and your password in the plugin...

Yes, I also need User/Password, but this fields are available in old and new Plugin.
It is working with dyndns1 and dyndns2 without "Force SSL" and when changing the backend from "ddclient" to "OPNsense".
I'm not sure if this is as intuitive and flexible as the old plugin... I think definitely not.

[chemlud]

Hi,
I have the same problem.
Is there any solution? Would be a big problem for me, because I cannot change the provider for several reasons.
In my case in the legacy dynamic dns client I can call for the Update URL:
https://update.twodns.de/update?hostname=myserver.dynvpn.de&ip=%IP%
I don't see that I can do this in the new one.
If I select "custom", I get a "Server" field, but that field only accepts servernames/IPs and not Update URLs. So
1. What is this field for
2. How to call Update URLs in the new DDNS plugin?

@1. Try: update.twodns.de
@2. Apparently no way to enter them directly, but the plugin will generate something along the line of your URL.

You don't need user name and password for updating? Really? Then leave these empty. Try DYNDNS2 and if that doesn't work try DYNDNS1 as "Method". Try with TLS, or maybe without.

PS:

According to this here

https://www.twodns.de/en/faqs#faq2

I would enter your email as user name and your password in the plugin...

Yes, I also need User/Password, but this fields are available in old and new Plugin.
It is working with dyndns1 and dyndns2 without "Force SSL" and when changing the backend from "ddclient" to "OPNsense".
I'm not sure if this is as intuitive and flexible as the old plugin... I think definitely not.

What do you mean: "changing the backend from "ddclient" to "OPNsense"?

[franco]

Since 23.1 you can avoid dealing with ddclient issues by using a OPNsense Python backend implementation instead. It implements Dyndns2 protocol (used by a number of providers) and Azure DNS currently.


Cheers,
Franco

[chemlud]

Since 23.1 you can avoid dealing with ddclient issues by using a OPNsense Python backend implementation instead. It implements Dyndns2 protocol (used by a number of providers) and Azure DNS currently.


Cheers,
Franco

So we have a third solution now and this is the way to go in the future? :-)

[franco]

Perhaps, but only if enough community resources go into providing further protocol support for the backend to be able to cover more providers deviating from the standard(s).


Cheers,
Franco

[chemlud]

... I use the ddns Plugin (new) in 22.7.last, works fine for two dyndns providers with Custom settings, so what would be needed to add these two to the drop-down menu?

[franco]

Which providers are these? From the looks of it the GUI just follows what ddclient thinks the underlying protocol is for the provider and your providers use a different one than dyndns2 then. That particular protocol would have to be added a Python code to bring the providers using it into the list.


Cheers,
Franco

[chemlud]

goip.de and ddnss.de, for both I use dyndns2.

"Server"s are www.goip.de and ddnss.de, just plain vanilla user name and password, "IP check method" is Interface at the moment.

"Force SSL" ist checked, I use ipv4 only...

[franco]

Perhaps these just work switching to OPNsense backend and using "dyndn2" provider then? They are current set as "custom", right?


Cheers,
Franco

[chemlud]

Yepp, custom, both... Thought you were interested in adding them to the drop-down to increase ootb user experience and satisfaction :-D

[xpendable]

So does the os-ddclient plugin even need to be installed if using the OPNsense backend?

[chemlud]

I had a look in the release notes

https://forum.opnsense.org/index.php?topic=32081.0

and documentation

https://docs.opnsense.org/manual/dynamic_dns.html

but can't find any details on the Python script mentioned by @Franco. Started to look in the GUI, finally found it in System -> Settings -> Cron (drop down...).

Apparently the new ddns plugin is not triggered by newwanip but rather spams the DynDNS provider with updates every 5 min (300 sec iirc). That was apparently not the case with the old plugin. For the Python script the default in the GUI is one update a day at 00:00.

The users of dyndns are now somewhere between a rock and a hrad place... :-(

Wouldn't if be possible to start the new Python script upon detection of a new WAN IP rather than at a fixed time interval? Just asking...