ddclient-devel is broken

[gstyle]

Ah interesting.

Can I then uninstall the os-ddclient plugin (when using the OPNsense backend)?
Or will I then lose my config or the complete Dynamic DNS Service?

[tidarp5]

Anyone able to use OPNsense backend in 23.1.6 with DuckDNS?

I've tried to use 'custom' and 'DynDns2' protocol with DuckDNS domain (as they also host a DynDns compatible endpoint). Always got this error as ddclient service always fail to start:

Code Select Expand

Error ddclient Unable to read file /var/tmp/ddclient_opn.status

seems to be the same issue mentioned here with no solution: https://forum.opnsense.org/index.php?topic=32355.msg160279#msg160279

[snippem]

Anybody a idea?
Want to use cloudflare ddns with ipv6.
I setup a aaaa record in cloudflare to point to. As a password I used the global API. 
See pictures for the settings this is with the mentioned patch and opnsense backend.
When I check the logs ddclient is trying to write an a record. This results in a error see the screen capture. Obviously the record that it should write is a aaaa record.

Okay my fault i didn't read the topic well. I have the same error with os-ddclient. I have opnsense as the backend and cloudflare setup as ipv4. I see one update of my ip-adres on cloudflare and then i get this error:
Error   ddclient   Unable to read file /var/tmp/ddclient_opn.status

For now using the os-dyndns hope there will be a solution as this is legacy and usable untill 23.7 arrives :-\


Verstuurd vanaf mijn CPH2449 met Tapatalk

[guest36947]

Anyone able to use OPNsense backend in 23.1.6 with DuckDNS?

I've tried to use 'custom' and 'DynDns2' protocol with DuckDNS domain (as they also host a DynDns compatible endpoint). Always got this error as ddclient service always fail to start:

Code Select Expand

Error ddclient Unable to read file /var/tmp/ddclient_opn.status

seems to be the same issue mentioned here with no solution: https://forum.opnsense.org/index.php?topic=32355.msg160279#msg160279

Yes there was a bug that I fixed, I am guessing you are using the interface as the IP source, change it to one of the web based ip sources for now and it should work

https://github.com/opnsense/plugins/pull/3406

[tidarp5]

Ah yes, I used the interface as the IP source. So that's why it's broken. After trying some other web based source, I found it works correctly with ipify-ipv4. Thanks!

And also for anyone else who use duckdns, the Hostnames needs to have only the sub-domain part of duckdns. For example, if your domain is 'my-domain.duckdns.org' , then just put 'my-domain' in Hostnames field.

[gpb]

Ah yes, I used the interface as the IP source. So that's why it's broken. After trying some other web based source, I found it works correctly with ipify-ipv4. Thanks!

And also for anyone else who use duckdns, the Hostnames needs to have only the sub-domain part of duckdns. For example, if your domain is 'my-domain.duckdns.org' , then just put 'my-domain' in Hostnames field.

Thanks for this.  Just to confirm settings, you're using backend:opnsense, service:dyndns2, both username and password (token), hostname (sub-domain segment only as noted above), check ip method:ipify-ipv4, interface to monitor:WAN, forcessl:checked.

I tried using dyndns as the check ip method and didn't get an error, but also no success message.  To confirm the log messages, this is what I'm seeing now.  (It's confusing I still see ddclient running as I thought backend:opnsense negated the need for that...confirm...?)

Code Select Expand

2023-04-24T09:02:39-04:00 Notice ddclient Flush dyndns status to disk
2023-04-24T09:02:39-04:00 Notice ddclient Account xxxxxxxxxxxxxxxxxxxxxxxxxx [dyndns2 - ] changed

[tidarp5]

Thanks for this.  Just to confirm settings, you're using backend:opnsense, service:dyndns2, both username and password (token), hostname (sub-domain segment only as noted above), check ip method:ipify-ipv4, interface to monitor:WAN, forcessl:checked.

You need to use the custom service to call to duckdns with dyndns protocol, service:dyndns2 will not do update to duckdns endpoint.

So backend is opnsense, but service:custom, protocol:dyndns2, server: www.duckdns.org. Username can be blank and password is token, check ip method:ipify-ipv4. See my attached image for screenshot.

These are the log messages when I get the success update:

Code Select Expand


2023-04-24T10:58:40 Notice ddclient Account [custom - Duck DNS DynDns] changed
2023-04-24T10:58:40 Notice ddclient Account [custom - Duck DNS DynDns] set new ip xxx.xx.xx.xxx [good]
2023-04-24T10:58:38 Notice ddclient Account [custom - Duck DNS DynDns] execute

Note that you might need to turn on verbose logging in General setting to get these debug logs.

[gpb]

@tidarp5 Thank you!  Much easier than trial and error.  :)

[CJ]

Ah yes, I used the interface as the IP source. So that's why it's broken. After trying some other web based source, I found it works correctly with ipify-ipv4. Thanks!

And also for anyone else who use duckdns, the Hostnames needs to have only the sub-domain part of duckdns. For example, if your domain is 'my-domain.duckdns.org' , then just put 'my-domain' in Hostnames field.

That's only the case for the OPNSense backend.  I'm still using ddclient and full hostname and interface checking still works.

[tidarp5]

@ CJRoss Yes, I should clarify that this is only for when you want to use OPNSense backend, custom service and dyndns2 protocol with duckdns.

[chemlud]

This incremental change was released today:

https://github.com/opnsense/plugins/blob/94d04f74c8481ea58a09aa707bde6245c9a1ef49/dns/ddclient/pkg-descr#L9-L14

We will keep doing these as requests and contributions come in. os-dyndns is scheduled for final removal in 23.7.


Cheers,
Franco

...was busy lately, just saw it today. Many thanks for clarification, so any kind of dynDNS service will be functional in 23.7 and onwards. Hope the ddlient will get some fixes, wouldn't like to switch to something new again on all installs...

The wrong update-status shown in logs for ddclient are not vary handy, have to play around with pind and stuff to test, if IP updates have been successful...