Dynamic DNS ddclient plugin not working for AWS R53.

[thereaper]

Looks like legacy plugin, dyndns, which worked perfectly with AWS, got dropped.

There is 25 pages long thread about ddclient issues:
https://forum.opnsense.org/index.php?topic=26446.360

I'm getting very strange errors, and the error srting "No address found for" is not even in source code ... How to debug it, please?


Or can we have legacy dyndns plugin back please?

Code Select Expand


2024-02-09T18:22:11 Warning ddclient No address found for 313-(redacted uuid)-483b3 [aws - ]
2024-02-09T18:16:59 Warning ddclient No address found for 313-(redacted uuid)-483b3 [aws - ]
2024-02-09T18:11:47 Warning ddclient No address found for 313-(redacted uuid)-483b3 [aws - ]
2024-02-09T18:08:13 Warning ddclient No address found for 313-(redacted uuid)-483b3 [aws - ]
2024-02-09T18:03:37 Warning ddclient No address found for 313-(redacted uuid)-483b3 [aws - ]
2024-01-17T12:35:04 Notice ddclient WARNING: file /usr/local/etc/ddclient.conf: file /usr/local/etc/ddclient.conf must not be accessible by others.
2024-01-17T12:35:04 Notice ddclient WARNING: file /usr/local/etc/ddclient.conf: file /usr/local/etc/ddclient.conf must be accessible only by its owner.
2024-01-17T12:35:04 Notice ddclient WARNING: file /usr/local/etc/ddclient.conf: file /usr/local/etc/ddclient.conf must be accessible only by its owner (fixed).
2023-12-20T11:04:17 Notice ddclient WARNING: file /usr/local/etc/ddclient.conf: file /usr/local/etc/ddclient.conf must not be accessible by others.
2023-12-20T11:04:17 Notice ddclient WARNING: file /usr/local/etc/ddclient.conf: file /usr/local/etc/ddclient.conf must be accessible only by its owner.
2023-12-20T11:04:17 Notice ddclient WARNING: file /usr/local/etc/ddclient.conf: file /usr/local/etc/ddclient.conf must be accessible only by its owner (fixed).


[mitchpleune]

Hi, Just wanted to say I had the exact same error, until I filled in some of the config options correctly. It took me a bit of bumbling to figure out. Here is what my config looks like, so you can copy:

Rule 1:

• Service: aws
• Username: IAM access key
• Password: IAM access key password
• Zone: Z066***************JI
• Hostname(s): home.p*******.com
• TTL: 300
• Check ip method: Interface (IPv6)
• Interface to monitor: WAN
• Check ip timeout: 10
• Force SSL: Checked

I cloned this to also use Interface IPv4, and left the general setttings as default (backend is native). This is working for me.

[ethan240]

Thanks mitchpleune, that worked for me

Attached images of my config (MAKE SURE TO CLICK APPLY)