1
23.1 Legacy Series / Re: ddclient-devel is broken
« on: April 27, 2023, 03:54:42 pm »
@ CJRoss Yes, I should clarify that this is only for when you want to use OPNSense backend, custom service and dyndns2 protocol with duckdns.
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
23.1 Legacy Series / Re: ddclient-devel is broken
« on: April 24, 2023, 04:01:55 pm »Quote
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]
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.
3
23.1 Legacy Series / Re: ddclient-devel is broken
« on: April 24, 2023, 06:23:57 am »
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.
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.
4
23.1 Legacy Series / Re: ddclient-devel is broken
« on: April 22, 2023, 06:11:45 am »
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:
seems to be the same issue mentioned here with no solution: https://forum.opnsense.org/index.php?topic=32355.msg160279#msg160279
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]
Error ddclient Unable to read file /var/tmp/ddclient_opn.statusseems to be the same issue mentioned here with no solution: https://forum.opnsense.org/index.php?topic=32355.msg160279#msg160279
5
23.1 Legacy Series / Re: DDNS IP/updated columns do not update
« on: February 18, 2023, 04:01:00 pm »
I start having this issue with duckdns since updated to 23.1.1 from 23.1_6, which is strange 
.
.
Pages: [1]